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.

Sign up for GitHub

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

Jump to bottom

Clarification on cg.hasMetadata #10

Closed
alanorth opened this issue Nov 7, 2019 · 0 comments
Closed

Clarification on cg.hasMetadata #10

alanorth opened this issue Nov 7, 2019 · 0 comments
Labels
question Further information is requested

Comments

@alanorth
Copy link
Collaborator

alanorth commented Nov 7, 2019

We had previously agreed that CGSpace would migrate its cg.identifier.dataurl field to cg.hasMetadata but I'm not sure those are the same thing. We have only about 450 uses of this field out of 80,000 items on CGSpace, but it seems that these generally link to data sets on Dataverse or partner sites, for example:

Can you think of a more appropriate DCTERMS or CG Core v2 field for us to put these? If not, I might just leave them in cg.identifier.dataurl for now. Thank you!
@alanorth alanorth added the question Further information is requested label Nov 7, 2019
alanorth added a commit to ilri/DSpace that referenced this issue Dec 18, 2019
@alanorth
Use cg.identifier.dataurl instead of cg.hasMetadata
bf61841 
This field is used to store URLs for external data files and does
not make sense to use as "hasMetadata". Reverting this change for
now.

See: AgriculturalSemantics/cg-core#10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alanorth