alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-11-25 16:08:19 +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
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 50 additions and 35 deletions
Show Stats 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: -->

45
docs/2019-01/index.html
View File

@ -27,7 +27,7 @@ I don&rsquo;t see anything interesting in the web server logs around that time t
" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-01/" /><meta property="article:published_time" content="2019-01-02T09:48:30&#43;02:00"/>
<meta property="article:modified_time" content="2019-01-16T17:10:50&#43;02:00"/>
<meta property="article:modified_time" content="2019-01-17T13:28:41&#43;02:00"/>
<meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="January, 2019"/>
@ -60,9 +60,9 @@ I don&rsquo;t see anything interesting in the web server logs around that time t
"@type": "BlogPosting",
"headline": "January, 2019",
"url": "https://alanorth.github.io/cgspace-notes/2019-01/",
"wordCount": "2447",
"wordCount": "2574",
"datePublished": "2019-01-02T09:48:30&#43;02:00",
"dateModified": "2019-01-16T17:10:50&#43;02:00",
"dateModified": "2019-01-17T13:28:41&#43;02:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -783,21 +783,8 @@ sys 0m2.396s
<ul>
<li>Send reminder to Atmire about purchasing the <a href="https://tracker.atmire.com/tickets-cgiar-ilri/view-ticket?id=657">MQM module</a></li>
<li>Trying to decide the solid action points for CGSpace on the CG Core 2.0 metadata:
<ul>
<li>dc.description → cg.description.notes</li>
<li>dc.description.abstract → dc.abstract</li>
<li>dc.description.version → cg.peer-reviewed (or cg.peer-review-status)</li>
<li>dc.description.sponsorship → cg.contributor.donor</li>
<li>dc.contributor.author → dc.creator</li>
<li>dc.language.iso → dc.language</li>
<li>cg.identifier.url → dc.identifier</li>
<li>dc.identifier.citation → dc.bibliographicCitation</li>
<li>dc.relation.ispartofseries → dc.relation.isPartOf</li>
<li>cg.targetaudience → dc.audience</li>
</ul></li>
<li>It&rsquo;s actually difficult to decide some of these because the current CG Core 2.0 document does not provide guidance or descriptions</li>
<li>Trying to decide the solid action points for CGSpace on the CG Core 2.0 metadata&hellip;</li>
<li>It&rsquo;s difficult to decide some of these because the current CG Core 2.0 document does not provide guidance or rationale (yet)!</li>
<li>Also, there is not a good Dublin Core reference (or maybe I just don&rsquo;t understand?)</li>
<li>Several authoritative documents on Dublin Core appear to be:
@ -809,6 +796,28 @@ sys 0m2.396s
<li>DSpace uses DCTERMS in the metadata it embeds in XMLUI item views!</li>
<li>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</li>
<li>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&hellip;</li>
<li>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</li>
<li>We might be able to use some proper fields for citation, abstract, etc that are part of DCTERMS</li>
<li>To make matters more confusing, there is also &ldquo;qualified Dublin Core&rdquo; that uses the original fifteen elements of legacy DC and qualifies them, like <code>dc.date.accessioned</code>
<ul>
<li>According to Wikipedia <a href="https://en.wikipedia.org/wiki/Dublin_Core">Qualified Dublin Core was superseded by DCTERMS in 2008</a>!</li>
</ul></li>
<li>So we should be trying to use DCTERMS where possible, unless it is some internal thing that might mess up DSpace (like dates)</li>
<li>&ldquo;Elements 1.1&rdquo; means legacy DC</li>
<li>Possible action list for CGSpace:
<ul>
<li>dc.description.abstract → dcterms.abstract</li>
<li>dc.description.version → cg.peer-reviewed (or cg.peer-review-status?)</li>
<li>dc.description.sponsorship → cg.contributor.donor</li>
<li>dc.contributor.author → dc.creator</li>
<li>dc.language.iso → dcterms.language</li>
<li>cg.identifier.url → dcterms.identifier</li>
<li>dc.identifier.citation → dcterms.bibliographicCitation</li>
<li>dc.relation.ispartofseries → dcterms.isPartOf</li>
<li>cg.targetaudience → dcterms.audience</li>
</ul></li>
</ul>
<!-- vim: set sw=2 ts=2: -->

10
docs/sitemap.xml
View File

@ -4,7 +4,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/2019-01/</loc>
<lastmod>2019-01-16T17:10:50+02:00</lastmod>
<lastmod>2019-01-17T13:28:41+02:00</lastmod>
</url>
<url>
@ -204,7 +204,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2019-01-16T17:10:50+02:00</lastmod>
<lastmod>2019-01-17T13:28:41+02:00</lastmod>
<priority>0</priority>
</url>
@ -215,7 +215,7 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2019-01-16T17:10:50+02:00</lastmod>
<lastmod>2019-01-17T13:28:41+02:00</lastmod>
<priority>0</priority>
</url>
@ -227,13 +227,13 @@
<url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2019-01-16T17:10:50+02:00</lastmod>
<lastmod>2019-01-17T13:28:41+02:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2019-01-16T17:10:50+02:00</lastmod>
<lastmod>2019-01-17T13:28:41+02:00</lastmod>
<priority>0</priority>
</url>