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

Missing MARC field 680 in RDF #333

Closed
acka47 opened this issue Dec 8, 2022 · 12 comments
Closed

Missing MARC field 680 in RDF #333

acka47 opened this issue Dec 8, 2022 · 12 comments
Assignees
Labels
upstream changes in upstream data/API needed
Projects

Comments

@acka47
Copy link
Contributor

acka47 commented Dec 8, 2022

Reported via email by @stefandesu for Cocoda. I opened a corresponding Jira issue at DNB: https://jira.dnb.de/browse/GND-226

Am 07.12.22 um 11:56 schrieb Peters, Stefan:

... Dabei ist mir aufgefallen, dass die Daten, die auf der Seite der DNB unter "Erläuterungen" stehen (also insb. Verwendungshinweise) nicht in lobid eingespielt sind.

Beispiel: 4053474-1 Schule
lobid: https://lobid.org/gnd/4053474-1
DNB: https://portal.dnb.de/opac.htm?method=simpleSearch&cqlMode=true&query=nid%3D4053474-1

Diese Daten wären jedoch für die Anzeige in Cocoda recht wichtig. Ich vermute, das Problem liegt daran, dass diese Daten nicht im RDF-Datensatz der DNB vorhanden sind, kann das sein? In MARC-XML sind sie vorhanden in Feld 680. Meinst du, es wäre möglich, diese Daten auch über lobid zu bekommen?

@acka47 acka47 added the upstream changes in upstream data/API needed label Dec 8, 2022
@acka47 acka47 added this to Backlog in lobid board via automation Dec 8, 2022
@stefandesu
Copy link

Is there any update on this? I don't have access to the DNB Jira, so I can't check myself.

@acka47
Copy link
Contributor Author

acka47 commented Apr 20, 2023

Is there any update on this?

Not yet. I have forwarded your question as this JIRA comment:

Ich leite mal die Frage des VZG-Kollegen Stefan Peters weiter: Gibt es hier irgendwelche Entwicklungen oder auch Angaben zum Zeitpunkt der geplanten Umsetzung?

@acka47
Copy link
Contributor Author

acka47 commented Apr 20, 2023

DNB responded quickly and positively:

die Anforderungen für die Ausgabe in RDF sind erstellt (Ticket: ILT-8227 ist mit diesem Ticket verknüpft, hast Du Zugriff drauf?).
Wenn alles gut geht, werden die Anforderungen im Import/Export-Release 2023.03 umgesetzt (Priorisierungstermin findet Anfang Mai statt).
Go-live für die Export-Formate ist der 26.09.2023.

@acka47
Copy link
Contributor Author

acka47 commented Oct 11, 2023

Update from DNB:

Die Änderung wurde produktiv genommen. Siehe https://d-nb.info/gnd/4427720-9/about/lds
Beim nächsten Dump (Ende Oktober/Anfang November) ist die Änderung dann auch mit drin.

@acka47
Copy link
Contributor Author

acka47 commented Oct 11, 2023

For implementing this, a new property was added to GND ontology: gndo:usingInstructions (see also the version notes of the current GNDO version). I added it with b8ee797 and will open a PR.

@acka47
Copy link
Contributor Author

acka47 commented Oct 13, 2023

With updates coming in that include the property https://d-nb.properties.info/standards/elementset/gnd#usingInstructions, we already get alert mails " Alert GND: found not compacted field(s)!":

On 13.10.23 01:04, sol wrote:

gnd_20221212.mappings.authority.properties.https://d-nb.properties.info/standards/elementset/gnd#usingInstructions.properties.@language.type
gnd_20221212.mappings.authority.properties.https://d-nb.properties.info/standards/elementset/gnd#usingInstructions.properties.@language.fields.keyword.type
gnd_20221212.mappings.authority.properties.https://d-nb.properties.info/standards/elementset/gnd#usingInstructions.properties.@value.type
gnd_20221212.mappings.authority.properties.https://d-nb.properties.info/standards/elementset/gnd#usingInstructions.properties.@value.fields.keyword.type

I am hopeful, this will be solved by just updating the context as in #356.

@stefandesu
Copy link

I see that gndo:usingInstructions is now part of the Lobid context. However, it doesn't seem like the values have been updated yet. Are there any entries with new updates that I can use to test this? When will old entries (see my original example) get the updated values?

Thanks!

@acka47
Copy link
Contributor Author

acka47 commented Nov 2, 2023

Hi @stefandesu ,

thanks for asking. Unfortunately, my assumption above was wrong:

I am hopeful, this will be solved by just updating the context as in #356.

  1. I forgot to set the language in the context which should be fixed with Fix @context for usingInstructions& professionOrOccupation #360
  2. The changes have not been deployed to production anyway but are only on https://test.lobid.org/gnd

We will let you know tomorrow when some entries are on test that actually look like what you can expect in the future.

@acka47 acka47 self-assigned this Nov 2, 2023
@acka47
Copy link
Contributor Author

acka47 commented Nov 3, 2023

We will let you know tomorrow when some entries are on test that actually look like what you can expect in the future.

Unfortunately, no resource with 680 was added/modified, so there is no example yet, see https://test.lobid.org/gnd/search?q=_exists_%3AusingInstructions++AND+describedBy.dateModified%3A2023-11-02.

However, it will just be an array of strings, e.g. in https://test.lobid.org/gnd/1269971174.json it will look like this:

{
   "usingInstructions":[
      "Weitere Titel ggf. auch unter dem Pseudonym bzw. dem wirklichen Namen"
   ]
}

@acka47
Copy link
Contributor Author

acka47 commented Nov 7, 2023

@stefandesu usingInstructions can now be found on production with the correct structure, see https://lobid.org/gnd/search?q=_exists_%3AusingInstructions&format=json

@stefandesu
Copy link

@acka47 Thanks a lot!

@acka47
Copy link
Contributor Author

acka47 commented Dec 11, 2023

Done, see above and #366 (comment) . Closing.

@acka47 acka47 closed this as completed Dec 11, 2023
lobid board automation moved this from Backlog to Done Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream changes in upstream data/API needed
Projects
Development

No branches or pull requests

2 participants