Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change labels for "Published/Unpublished" in Authorities #1600

Open
jenniferward opened this issue Jun 12, 2024 · 10 comments
Open

Change labels for "Published/Unpublished" in Authorities #1600

jenniferward opened this issue Jun 12, 2024 · 10 comments

Comments

@jenniferward
Copy link
Contributor

In the Authorities, “Unpublished” doesn’t mean “Unpublished” it means “Now you can merge”. This differs from Sources, where "unpublished/published" has an effect on what gets pushed to the public platforms.

image

The terms are confusing in Authorities for users. The terms in authorities should be changed to reflect the actual function. This should not affect Sources at all!

"Published" is the term that is visible on almost all records.

Wrong suggestions first:

  • Merger/Mergee
  • Keep this record / Delete this record
  • Reunificator / Reunificatee
  • Der Titelzumbeibehaltende / Der Titelzumumhängende

Maybe just Published / To be merged?

@MFalletta
Copy link

What is meant by "Der Titelzumbeibehaltende / Der Titelzumumhängende"?

I suggest: Der beizubehaltende Titel / Der umzuhängende Titel

@jenniferward
Copy link
Contributor Author

Just a bad joke ;-)

@xhero
Copy link
Contributor

xhero commented Jun 12, 2024

I vote for "Der Titelzumbeibehaltende / Der Titelzumumhängende" as the label ;)

@ahankinson
Copy link
Contributor

Is it worth exploring whether this is actually the right place for this marker, or if it should be in its own place? A “merge control” section of the record?

@xhero
Copy link
Contributor

xhero commented Jun 12, 2024

Well it is kinda of a hack in the first place to use wf_stage for merging..

@jenniferward
Copy link
Contributor Author

And it's really "relinking" not merging (for actual merging, see the fairy tale I wrote here: #1259)

@Docudoctor
Copy link

Docudoctor commented Jun 12, 2024 via email

@fjorba
Copy link
Contributor

fjorba commented Jun 13, 2024

We have began to work on merging authority records. Our workflow is surely different from yours, but also, we have been bitten by the fact that the merge only works if in the table the id column is labeled RISM ID. It turns out that we are not RISM, so this is one of the things that we have customized, via translation files. That's why we cannot use the official Muscat merge tool. Plus, we think that it requires more steps than we are used to in our current (locally developed) Invenio merge tool.

We have been doing some brainstorming and we have a provisional convention that, for the time being, allows us to mark records for merging. Imagine that there is a bad record 4321 that we want to be merged into the good record 1234. What we do is to write in the comments box of the good record box +4321. This convention also allows that in a single step more than one bad records are merged in a good one, writing more than one +recid. It is also very simple to verifiy the right syntax of those messages (only one or more groups of + and digits). It permits also know who did the merge (or the petition to merge it) and even keep track of it, if necessary. At this moment the merge is done in batch using a cron job (not finished yet), but it could be done right in the moment using some of the Rails hooks when writing the comment.

This convention allows that any person, with or without the rights to merge records, can spot and mark a duplicated record to merged (the more eyes, the better). We haven't finished yet our roles-and-permisions layout, but the idea is that if a person without the rights writes this mark, then the right person reviews it and repeats (copy & paste) or not, the same comment and this one is the one that is performed, and both are deleted (for the time being, only archived).

@fjorba
Copy link
Contributor

fjorba commented Jun 13, 2024

Having said that, in our case, the existence of statuses for authority records is still useful. For example, at this moment, our bad records, after being merged, are put into Delete state. And we were also brainstorming about finding a good use of those statuses, like Published for those that have been verified (for example, our Faculties and Departments, and our Faculty staff), and Unpublished for those not verified. So yes, those statuses are important for us.

So, Validated and Not validated could work also for you?

@jenniferward
Copy link
Contributor Author

Since only editors can merge, the published/unpublished options (or whatever it will be called) should not be accessible to catalogers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants