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

Add notes for 2019-01-17

Browse Source
This commit is contained in:
Alan Orth 2019-01-17 13:28:41 +02:00
parent 8a0e7abd6c
commit 97db64f1a7
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 208 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -361,8 +361,51 @@ $ time http --print h 'https://digitalarchive.worldfishcenter.org/rest/items?exp
## 2019-01-16 ## 2019-01-16
- Day three of CGSpace AReS meeting in Amman - Day three of CGSpace AReS meeting in Amman
- We discussed CGcore and decided some action points - We discussed CG Core 2.0 metadata and decided some action points
- We discussed branding of AReS tool - We discussed branding of AReS tool
- Notes from our CG Core 2.0 metadata discussion:
- Not Dublin Core:
- dc.subtype
- dc.peer-reviewed
- Dublin Core, possible action for CGSpace:
- dc.description:
- We use dc.description.abstract, dc.description (Notes), dc.description.version (Peer review status), dc.description.sponsorship (Funder)
- Maybe move abstract to dc.description
- Maybe notes moves to cg.description.notes???
- Maybe move dc.description.version to cg.peer-reviewed or cg.peer-review-status???
- Move dc.description.sponsorship to cg.contributor.donor???
- dc.subject:
- Wait for guidance, evaluate technical implications (Google indexing, OAI, etc)
- Move dc.contributor.author to dc.creator
- dc.contributor Project
- Recommend against creating new fields for all projects
- We use collections projects/themes/etc
- dc.contributor Project Lead Center
- MELSpace uses cg.contributor.project-lead-institute (institute is more generic than center)
- Maybe we use?
- dc.contributor Partner
- Wait for guidance
- MELSpace uses cg.contibutor.center (?)
- dc.contributor Donor
- Use cg.contributor.donor
- dc.date
- Wait for guidance, maybe move dc.date.issued?
- dc.date.accessioned and dc.date.available are automatic in DSpace
- dc.language
- Move dc.language.iso to dc.language
- dc.identifier
- Move cg.identifier.url to dc.identifier
- dc.identifier bibliographicCitation
- dc.identifier.citation should move to dc.bibliographicCitation
- dc.description.notes
- Wait for guidance, maybe move to cg.description.notes ???
- dc.relation
- Maybe move cg.link.reference
- Perhaps consolodate cg.link.audio etc there...?
- dc.relation.isPartOf
- Move dc.relation.ispartofseries to dc.relation.isPartOf
- dc.audience
- Move cg.targetaudience to dc.audience
- Something happened to the Solr usage statistics on CGSpace - Something happened to the Solr usage statistics on CGSpace
- I looked on the server and the Solr cores are there (56GB!), and I don't see any obvious errors in dmesg or anything - I looked on the server and the Solr cores are there (56GB!), and I don't see any obvious errors in dmesg or anything
- I see that the server hasn't been rebooted in 26 days so I rebooted it - I see that the server hasn't been rebooted in 26 days so I rebooted it
@ -487,6 +530,10 @@ Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
![Solr stats working](/cgspace-notes/2019/01/solr-stats-incorrect.png) ![Solr stats working](/cgspace-notes/2019/01/solr-stats-incorrect.png)
- Some StackOverflow discussions related to this:
- https://stackoverflow.com/questions/2895417/solrexception-internal-server-error/3035916#3035916
- https://stackoverflow.com/questions/11683850/how-much-memory-could-vm-use
- https://stackoverflow.com/questions/8892143/error-when-opening-a-lucene-index-map-failed/8893684#8893684
- Abenet was asking if the Atmire Usage Stats are correct because they are over 2 million the last few months... - Abenet was asking if the Atmire Usage Stats are correct because they are over 2 million the last few months...
- For 2019-01 alone the Usage Stats are already around 1.2 million - For 2019-01 alone the Usage Stats are already around 1.2 million
- I tried to look in the nginx logs to see how many raw requests there are so far this month and it's about 1.4 million: - I tried to look in the nginx logs to see how many raw requests there are so far this month and it's about 1.4 million:
@ -500,4 +547,28 @@ user 0m16.205s
sys 0m2.396s 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
- 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/)
- [DCMI Metadata Terms](http://www.dublincore.org/documents/dcmi-terms/)
- And what is the relationship between DC and DCTERMS?
- 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...
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

135
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: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="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-16T16:47:30&#43;02:00"/> <meta property="article:modified_time" content="2019-01-16T17:10:50&#43;02:00"/>
<meta name="twitter:card" content="summary"/> <meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="January, 2019"/> <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", "@type": "BlogPosting",
"headline": "January, 2019", "headline": "January, 2019",
"url": "https://alanorth.github.io/cgspace-notes/2019-01/", "url": "https://alanorth.github.io/cgspace-notes/2019-01/",
"wordCount": "2079", "wordCount": "2447",
"datePublished": "2019-01-02T09:48:30&#43;02:00", "datePublished": "2019-01-02T09:48:30&#43;02:00",
"dateModified": "2019-01-16T16:47:30&#43;02:00", "dateModified": "2019-01-16T17:10:50&#43;02:00",
"author": { "author": {
"@type": "Person", "@type": "Person",
"name": "Alan Orth" "name": "Alan Orth"
@ -535,9 +535,97 @@ In [14]: for row in result.fetchone():
<li>Day three of CGSpace AReS meeting in Amman <li>Day three of CGSpace AReS meeting in Amman
<ul> <ul>
<li>We discussed CGcore and decided some action points</li> <li>We discussed CG Core 2.0 metadata and decided some action points</li>
<li>We discussed branding of AReS tool</li> <li>We discussed branding of AReS tool</li>
</ul></li> </ul></li>
<li>Notes from our CG Core 2.0 metadata discussion:
<ul>
<li>Not Dublin Core:</li>
<li>dc.subtype</li>
<li>dc.peer-reviewed</li>
<li>Dublin Core, possible action for CGSpace:</li>
<li>dc.description:
<ul>
<li>We use dc.description.abstract, dc.description (Notes), dc.description.version (Peer review status), dc.description.sponsorship (Funder)</li>
<li>Maybe move abstract to dc.description</li>
<li>Maybe notes moves to cg.description.notes???</li>
<li>Maybe move dc.description.version to cg.peer-reviewed or cg.peer-review-status???</li>
<li>Move dc.description.sponsorship to cg.contributor.donor???</li>
</ul></li>
<li>dc.subject:
<ul>
<li>Wait for guidance, evaluate technical implications (Google indexing, OAI, etc)</li>
</ul></li>
<li>Move dc.contributor.author to dc.creator</li>
<li>dc.contributor Project
<ul>
<li>Recommend against creating new fields for all projects</li>
<li>We use collections projects/themes/etc</li>
</ul></li>
<li>dc.contributor Project Lead Center
<ul>
<li>MELSpace uses cg.contributor.project-lead-institute (institute is more generic than center)</li>
<li>Maybe we use?</li>
</ul></li>
<li>dc.contributor Partner
<ul>
<li>Wait for guidance</li>
<li>MELSpace uses cg.contibutor.center (?)</li>
</ul></li>
<li>dc.contributor Donor
<ul>
<li>Use cg.contributor.donor</li>
</ul></li>
<li>dc.date
<ul>
<li>Wait for guidance, maybe move dc.date.issued?</li>
<li>dc.date.accessioned and dc.date.available are automatic in DSpace</li>
</ul></li>
<li>dc.language
<ul>
<li>Move dc.language.iso to dc.language</li>
</ul></li>
<li>dc.identifier
<ul>
<li>Move cg.identifier.url to dc.identifier</li>
</ul></li>
<li>dc.identifier bibliographicCitation
<ul>
<li>dc.identifier.citation should move to dc.bibliographicCitation</li>
</ul></li>
<li>dc.description.notes
<ul>
<li>Wait for guidance, maybe move to cg.description.notes ???</li>
</ul></li>
<li>dc.relation
<ul>
<li>Maybe move cg.link.reference</li>
<li>Perhaps consolodate cg.link.audio etc there&hellip;?</li>
</ul></li>
<li>dc.relation.isPartOf
<ul>
<li>Move dc.relation.ispartofseries to dc.relation.isPartOf</li>
</ul></li>
<li>dc.audience
<ul>
<li>Move cg.targetaudience to dc.audience</li>
</ul></li>
</ul></li>
<li>Something happened to the Solr usage statistics on CGSpace <li>Something happened to the Solr usage statistics on CGSpace
<ul> <ul>
@ -671,6 +759,13 @@ Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
<p><img src="/cgspace-notes/2019/01/solr-stats-incorrect.png" alt="Solr stats working" /></p> <p><img src="/cgspace-notes/2019/01/solr-stats-incorrect.png" alt="Solr stats working" /></p>
<ul> <ul>
<li>Some StackOverflow discussions related to this:
<ul>
<li><a href="https://stackoverflow.com/questions/2895417/solrexception-internal-server-error/3035916#3035916">https://stackoverflow.com/questions/2895417/solrexception-internal-server-error/3035916#3035916</a></li>
<li><a href="https://stackoverflow.com/questions/11683850/how-much-memory-could-vm-use">https://stackoverflow.com/questions/11683850/how-much-memory-could-vm-use</a></li>
<li><a href="https://stackoverflow.com/questions/8892143/error-when-opening-a-lucene-index-map-failed/8893684#8893684">https://stackoverflow.com/questions/8892143/error-when-opening-a-lucene-index-map-failed/8893684#8893684</a></li>
</ul></li>
<li>Abenet was asking if the Atmire Usage Stats are correct because they are over 2 million the last few months&hellip;</li> <li>Abenet was asking if the Atmire Usage Stats are correct because they are over 2 million the last few months&hellip;</li>
<li>For 2019-01 alone the Usage Stats are already around 1.2 million</li> <li>For 2019-01 alone the Usage Stats are already around 1.2 million</li>
<li>I tried to look in the nginx logs to see how many raw requests there are so far this month and it&rsquo;s about 1.4 million:</li> <li>I tried to look in the nginx logs to see how many raw requests there are so far this month and it&rsquo;s about 1.4 million:</li>
@ -684,6 +779,38 @@ user 0m16.205s
sys 0m2.396s sys 0m2.396s
</code></pre> </code></pre>
<h2 id="2019-01-17">2019-01-17</h2>
<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>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:
<ul>
<li><a href="http://dublincore.org/documents/dces/">Dublin Core Metadata Element Set, Version 1.1: Reference Description</a></li>
<li><a href="http://www.dublincore.org/documents/dcmi-terms/">DCMI Metadata Terms</a></li>
</ul></li>
<li>And what is the relationship between DC and DCTERMS?</li>
<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>
</ul>
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

10
docs/sitemap.xml
View File

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