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

[GND editor] Field 930 not displaying actual work title #1662

Open
afaschon opened this issue Nov 7, 2024 · 6 comments
Open

[GND editor] Field 930 not displaying actual work title #1662

afaschon opened this issue Nov 7, 2024 · 6 comments
Assignees

Comments

@afaschon
Copy link

afaschon commented Nov 7, 2024

When a source record is part of a collection, field 930, "Werktitel", shows the collection’s title instead of the actual work’s title:
werktitel_1

Instead, field 930 should be displaying the work’s title as in 100 $p.
werktitel_2

In this example case, "Werktitel" should show "Pater noster qui es in coelis", not "Cantiones sacrae de festis praecipuis totius anni".

@xhero xhero assigned xhero and lpugin Nov 7, 2024
@xhero
Copy link
Contributor

xhero commented Nov 7, 2024

What is 100$p in the Work Node? To me it seems correct in the example, as it is pointing to Work Node $t, which is called "work title". $p at the moment is not configured in the editor.

@afaschon
Copy link
Author

afaschon commented Nov 7, 2024

From a technical point of view, it is correct, yes. From a user’s point of view it is misleading because the work node is not about any collection a work may or may not be part of but about the individual work (there are also many works that are not part of any collection—their title is displayed correctly).

One problem is that in the GND’s standards, the collection title is a mandatory part of the work title. But we don’t want the collection title to be displayed before the individual work’s title because that is counter-intuitive from most researching points of view.

Is there, in your eyes, any solution to this?

@xhero
Copy link
Contributor

xhero commented Nov 7, 2024

Ok I see! There are a couple solutions, and it depends mostly from the data you want to have in $t and $p. The easiest solution is that one contains always the (eventual) collection name, and the other always the work title - either one is good for me. For example, $p could always be the collection, and we always put the title in $t, or viceversa.
It becomes more shady if $t sometimes has to be a collection name and sometimes a work title, which is the case I would like to avoid.

@afaschon
Copy link
Author

Thank you! Desiree and I are discussing the problem and we’ll get back to you asap.

@xhero
Copy link
Contributor

xhero commented Nov 14, 2024

Would merging the two fields, when importing the WorkNode, into $t work? In this case you would get: $tCantionae sacrae: Pater noster or formatted in a similar way, and you would see this in the Source when the WN is linked.

@lpugin
Copy link
Contributor

lpugin commented Nov 14, 2024

@afaschon please add links to the Muscat and GND records you are referring to in your next comments. Thanks!

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

3 participants