Remove "primary" selection from author merge tool

[RayBB]

Proposal

Based on a discussion on Slack back in July.

We do not need to have a "primary" selection in the author merge tool.

As I understand it, @seabelis says we should always have the oldest OLID as the "primary".

As such, we can dramatically simplify the GUI the author merge (and later work merge) by removing the "primary" ratio button from the GUI.

On the backend, there will still be a primary but it should automatically be selected based on which is the oldest ID.

Current design of the author merge page

I imagine the end result should look something like this:

Perhaps we link to the docs for merging :)

Justification

The main reason I want this change is to simplify the experience for librarians and keep our UIs nice.

Breakdown

Requirements Checklist

• [ ]

Related files

Stakeholders

• @seabelis @cdrini

---

Instructions for Contributors

Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.

[zorae]

Make sure to handle cases in which the librarian deselects what would otherwise be the primary record

[mheiman]

This may be fine, but I want to be sure we've thought it through. We have a lot of practices that are essentially "You should always do X (unless there's a very good reason to do Y)" so I'm wary of changes that make it impossible to do Y.

[seabelis]

The case where you don't want to include the first listed author in the merge at all does exist.

[RayBB]

@seabelis in this case I'd expect that the person merging could select the 2nd and 3rd authors (for example). Or is there an edge case I'm missing?

[seabelis]

No, probably I was missing something. As long as that remains possible, all good.