mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2020-04-12
This commit is contained in:
@ -89,6 +89,34 @@ $ ./add-orcid-identifiers-csv.py -i 2020-04-07-fix-duplicate-orcids.csv -db dspa
|
||||
- I ran the fixes on DSpace Test and CGSpace as well
|
||||
- I started testing the [pull request](https://github.com/ilri/DSpace/pull/445) sent by Atmire yesterday
|
||||
- I notice that we now need `yarn` to build, and I need to bump the Node.js `engine` version in our Mirage 2 theme in order to get it to build on Node.js 10.x
|
||||
- Font Awesome icons for GitHub etc weren't loading, and after a bit of troubleshooting I replaced version 4.5.0 with 5.13.0 and to my surprise they now include Mendeley and ORCID so we can get rid of the Academicons dependency
|
||||
|
||||
## 2020-04-12
|
||||
|
||||
- Testing the Atmire DSpace 6.3 code with a clean CGSpace DSpace 5.8 database snapshot
|
||||
- One Flyway migration failed so I had to manually remove it (and of course create the pgcrypto extension):
|
||||
|
||||
```
|
||||
dspace63=# DELETE FROM schema_version WHERE version IN ('5.8.2015.12.03.3');
|
||||
dspace63=# CREATE EXTENSION pgcrypto;
|
||||
```
|
||||
|
||||
- Then DSpace 6.3 started up OK and I was able to see some statistics in the Content and Usage Analysis (CUA) module, but not on community, collection, or item pages
|
||||
- I also noticed at least one of these errors in the DSpace log:
|
||||
|
||||
```
|
||||
2020-04-12 16:34:33,363 ERROR com.atmire.dspace.app.xmlui.aspect.statistics.editorparts.DataTableTransformer @ java.lang.IllegalArgumentException: Invalid UUID string: 1
|
||||
```
|
||||
|
||||
- And I remembered I actually need to run the DSpace 6.4 Solr UUID migrations:
|
||||
|
||||
```
|
||||
$ export JAVA_OPTS="-Xmx1024m -Dfile.encoding=UTF-8"
|
||||
$ ~/dspace63/bin/dspace solr-upgrade-statistics-6x
|
||||
```
|
||||
|
||||
- Run system updates on DSpace Test (linode26) and reboot it
|
||||
- More work on the DSpace 6.3 stuff, improving the GDPR consent logic to use [haven](https://github.com/chiiya/haven) instead of cookieconsent
|
||||
- It works better by injecting the Google Analytics script after the user clicks agree, and it also has a preferences section that gets automatically injected on the privacy page!
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
|
Reference in New Issue
Block a user