-
Notifications
You must be signed in to change notification settings - Fork 7
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
wrong values in hasVersion
and related
#1242
Comments
as discussed off-board woth @dr0i : I split this issue in two steps:
|
Both transformations were not set up correctly.
Deployed, see e.g. See e.g. https://alma.lobid.org/resources/search?q=HT000161712&format=json. Closed. |
Reopen for remodelling |
I am irritated by the definition of "hasVersion" as lobid is using it: e26a318
655 is only refering to electronic links in the metadata. In contrast https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/hasVersion gives a much broader definition:
I think this does not fit conceptually. Do we need this very narrow link list at all? Or should we even remodel the hasVersion? |
The values in 856## $3 which used to be 655 $3 and specifiy the content of the link are:
None of those has a specific refrence to versions of the publication. As discussed with @acka47 off-board I will leave out hasVersion for now. |
This makes these fields queryable, like: http://alma.lobid.org/resources/search?q=related.issn:%220955-8810%22&format=json See #1242.
e.g. HT000161712
The text was updated successfully, but these errors were encountered: