Update notes for 2019-08-29

This commit is contained in:
2019-08-29 19:25:06 +03:00
parent f063085aad
commit e6904be23c
3 changed files with 75 additions and 8 deletions

View File

@ -312,4 +312,30 @@ $ ./fix-metadata-values.py -i /tmp/authors.csv -db dspace -u dspace -p 'fuuu' -f
- I very well might run these on CGSpace soon...
## 2019-08-29
- Resume working on the CG Core v2 changes in the `5_x-cgcorev2` branch again
- I notice that CG Core doesn't currently have a field for CGSpace's "alternative title" (`dc.title.alternative`), but DCTERMS has `dcterms.alternative` so I [raised an issue about adding it](https://github.com/AgriculturalSemantics/cg-core/issues/9)
- Marie responded and said she would add `dcterms.alternative`
- I created a sed script file to perform some replacements of metadata on the XMLUI XSL files:
```
$ find dspace/modules/xmlui-mirage2/src/main/webapp/themes -iname "*.xsl" -exec ./cgcore-xsl-replacements.sed {} \;
```
- I think I got everything in the XMLUI themes, but there may be some things I should check once I get a deployment up and running:
- Need to assess the XSL changes to see if things like `not(@qualifier)]` still make sense after we move fields from DC to DCTERMS, as some fields will no longer have qualifiers
- Do I need to edit the author links to remove `dc.contributor.author` in `0_CGIAR/xsl/aspect/artifactbrowser/item-list-alterations.xsl`?
- Do I need to edit the author links to remove `dc.contributor.author` in `0_CGIAR/xsl/aspect/discovery/discovery-item-list-alterations.xsl`?
- Thierry Lewadle asked why some PDFs on CGSpace open in the browser and some download
- I told him it is because of the "content disposition" that causes DSpace to tell the browser to open or download the file based on its file size (currently around 8 megabytes)
- Peter asked why [an item on CGSpace](https://hdl.handle.net/10568/97825) has no Altmetric donut on the item view, but has one in our explorer
- I looked in the network requests when loading the CGSpace item view and I see the following response to the Altmetric API call:
```
"handles":["10986/30568","10568/97825"],"handle":"10986/30568"
```
- So this is the same issue we had before, where Altmetric *knows* this Handle is associated with a DOI that has a score, but the client-side JavaScript code doesn't show it because it seems to a secondary handle or something
<!-- vim: set sw=2 ts=2: -->