mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2019-01-17
This commit is contained in:
@ -361,8 +361,51 @@ $ time http --print h 'https://digitalarchive.worldfishcenter.org/rest/items?exp
|
||||
## 2019-01-16
|
||||
|
||||
- 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
|
||||
- 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
|
||||
- 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
|
||||
@ -487,6 +530,10 @@ Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
|
||||
|
||||

|
||||
|
||||
- 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...
|
||||
- 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:
|
||||
@ -500,4 +547,28 @@ user 0m16.205s
|
||||
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: -->
|
||||
|
Reference in New Issue
Block a user