alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Update notes for 2019-01-17

Browse Source
This commit is contained in:
Alan Orth
2019-01-17 19:53:00 +02:00
parent 97db64f1a7
commit 0c3d26d668
3 changed files with 50 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
content/posts/2019-01.md
View File

@ -550,18 +550,8 @@ sys 0m2.396s
## 2019-01-17
- Send reminder to Atmire about purchasing the [MQM module](https://tracker.atmire.com/tickets-cgiar-ilri/view-ticket?id=657)
- Trying to decide the solid action points for CGSpace on the CG Core 2.0 metadata:
- dc.description → cg.description.notes
- dc.description.abstract → dc.abstract
- dc.description.version → cg.peer-reviewed (or cg.peer-review-status)
- dc.description.sponsorship → cg.contributor.donor
- dc.contributor.author → dc.creator
- dc.language.iso → dc.language
- cg.identifier.url → dc.identifier
- dc.identifier.citation → dc.bibliographicCitation
- dc.relation.ispartofseries → dc.relation.isPartOf
- cg.targetaudience → dc.audience
- It's actually difficult to decide some of these because the current CG Core 2.0 document does not provide guidance or descriptions
- Trying to decide the solid action points for CGSpace on the CG Core 2.0 metadata...
- It's difficult to decide some of these because the current CG Core 2.0 document does not provide guidance or rationale (yet)!
- Also, there is not a good Dublin Core reference (or maybe I just don't understand?)
- Several authoritative documents on Dublin Core appear to be:
- [Dublin Core Metadata Element Set, Version 1.1: Reference Description](http://dublincore.org/documents/dces/)
@ -570,5 +560,21 @@ sys 0m2.396s
- DSpace uses DCTERMS in the metadata it embeds in XMLUI item views!
- We really need to look at this more carefully and see the impacts that might be made from switching core fields like languages, abstract, authors, etc
- We can check WorldFish and MELSpace repositories to see what effects these changes have had on theirs because they have already adopted some of these changes...
- I think I understand the difference between DC and DCTERMS finally: DC is the original set of fifteen elements and DCTERMS is the newer version that was supposed to address much of the drawbacks of the original with regards to digital content
- We might be able to use some proper fields for citation, abstract, etc that are part of DCTERMS
- To make matters more confusing, there is also "qualified Dublin Core" that uses the original fifteen elements of legacy DC and qualifies them, like `dc.date.accessioned`
- According to Wikipedia [Qualified Dublin Core was superseded by DCTERMS in 2008](https://en.wikipedia.org/wiki/Dublin_Core)!
- So we should be trying to use DCTERMS where possible, unless it is some internal thing that might mess up DSpace (like dates)
- "Elements 1.1" means legacy DC
- Possible action list for CGSpace:
- dc.description.abstract → dcterms.abstract
- dc.description.version → cg.peer-reviewed (or cg.peer-review-status?)
- dc.description.sponsorship → cg.contributor.donor
- dc.contributor.author → dc.creator
- dc.language.iso → dcterms.language
- cg.identifier.url → dcterms.identifier
- dc.identifier.citation → dcterms.bibliographicCitation
- dc.relation.ispartofseries → dcterms.isPartOf
- cg.targetaudience → dcterms.audience
<!-- vim: set sw=2 ts=2: -->