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

No URI in OAI-PMH records (with oai-ddi metadata prefix) #7786

Closed
tvi-cdsp opened this issue Apr 12, 2021 · 6 comments · Fixed by #7984
Closed

No URI in OAI-PMH records (with oai-ddi metadata prefix) #7786

tvi-cdsp opened this issue Apr 12, 2021 · 6 comments · Fixed by #7984

Comments

@tvi-cdsp
Copy link

From our understanding, we could have an URI Provided inside a metadata "holdings" tag pointing to the dataset (in the form of an URL https://doi.org/… rather than the DOI itself doi:10.21410/7E4/SRVNPE).
This uri, in ddi-codebook 2.5 xml, should be in codeBook -> docDscr -> citation -> holdings or/and codeBook -> stdyDscr -> citation -> holdings

This should allow Dataverse to provide "self sufficient" records in OAI-PMH records.

Example of desired result : http://services.fsd.tuni.fi/v0/oai?verb=GetRecord&identifier=oai:fsd.uta.fi:FSD1262&metadataPrefix=oai_ddi25

@gmi-cdsp
Copy link

Hi !

From a recent discussion around CESSDA data catalogue, it would be a better practice to use the first:
<pr:Used xpath="/codeBook/stdyDscr/citation/holdings/@URI" isRequired="true">

@jggautier
Copy link
Contributor

Hi @gmi-cdsp and @tvi-cdsp. Could you write a little more what you mean by "self sufficient"? I'm just curious :)

@gmi-cdsp
Copy link

gmi-cdsp commented May 4, 2021

Hi Julian. I guess we meant both that conforms to the DDI standard and that provides records including a URI. This URI would be displayed without transformation (self sufficient would mean clickable in that regard)?

@jggautier
Copy link
Contributor

Ah thanks, makes sense to me!

@qqmyers
Copy link
Member

qqmyers commented May 11, 2021

From the description and example in the DDI documentation for the holdings element, it looks like putting file information as multiple holdings elements (with the file page URI/file DOI as the URIs) might be a better practice. I see right now that files are currently listed as other Materials (otherMat).
Does such a change make sense? Or are there services that expect files in otherMat?

@tvi-cdsp
Copy link
Author

It seems to be a better practice indeed, sadly i cant speak about other services using otherMat.
I might be missing something, but it seems to me that modifying otherMat elements and adding a holdings element to docDscr and stdyDscr citation containing the doi url are two separate issues? Am I missing something here?

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

Successfully merging a pull request may close this issue.

4 participants