mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-12-21 20:52:18 +01:00
Update notes
This commit is contained in:
parent
89d1b61442
commit
64b8957945
@ -49,4 +49,10 @@ id=181 AND h.resource_type_id=2 AND h.resource_id IN (SELECT uuid FROM item WHER
|
||||
COPY 396
|
||||
```
|
||||
|
||||
## 2024-07-18
|
||||
|
||||
- I experimented with adding a regular expression to validate DOIs to the submission form
|
||||
- It is a slightly modified version of the one found here: https://stackoverflow.com/questions/27910/finding-a-doi-in-a-document-or-page
|
||||
- I decided it will probably be confusing to people and will have limited benefit, since we are normalizing most forms of DOIs to our preferred form after submission anyway
|
||||
|
||||
<!-- vim: set sw=2 ts=2: -->
|
||||
|
@ -34,7 +34,7 @@ Last week I had increased the limit from 30 to 60, which seemed to help, but now
|
||||
$ psql -c 'SELECT * from pg_stat_activity;' | grep idle | grep -c cgspace
|
||||
78
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ Replace lzop with xz in log compression cron jobs on DSpace Test—it uses less
|
||||
-rw-rw-r-- 1 tomcat7 tomcat7 387K Nov 18 23:59 dspace.log.2015-11-18.lzo
|
||||
-rw-rw-r-- 1 tomcat7 tomcat7 169K Nov 18 23:59 dspace.log.2015-11-18.xz
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -28,7 +28,7 @@ Move ILRI collection 10568/12503 from 10568/27869 to 10568/27629 using the move_
|
||||
I realized it is only necessary to clear the Cocoon cache after moving collections—rather than reindexing—as no metadata has changed, and therefore no search or browse indexes need to be updated.
|
||||
Update GitHub wiki for documentation of maintenance tasks.
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ I noticed we have a very interesting list of countries on CGSpace:
|
||||
Not only are there 49,000 countries, we have some blanks (25)…
|
||||
Also, lots of things like “COTE D`LVOIRE” and “COTE D IVOIRE”
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -28,7 +28,7 @@ Looking at issues with author authorities on CGSpace
|
||||
For some reason we still have the index-lucene-update cron job active on CGSpace, but I’m pretty sure we don’t need it as of the latest few versions of Atmire’s Listings and Reports module
|
||||
Reinstall my local (Mac OS X) DSpace stack with Tomcat 7, PostgreSQL 9.3, and Java JDK 1.7 to match environment on CGSpace server
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ After running DSpace for over five years I’ve never needed to look in any
|
||||
This will save us a few gigs of backup space we’re paying for on S3
|
||||
Also, I noticed the checker log has some errors we should pay attention to:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ There are 3,000 IPs accessing the REST API in a 24-hour period!
|
||||
# awk '{print $1}' /var/log/nginx/rest.log | uniq | wc -l
|
||||
3168
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ This is their publications set: http://ebrary.ifpri.org/oai/oai.php?verb=ListRec
|
||||
You can see the others by using the OAI ListSets verb: http://ebrary.ifpri.org/oai/oai.php?verb=ListSets
|
||||
Working on second phase of metadata migration, looks like this will work for moving CPWF-specific data in dc.identifier.fund to cg.identifier.cpwfproject and then the rest to dc.description.sponsorship
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -44,7 +44,7 @@ dspacetest=# select text_value from metadatavalue where metadata_field_id=3 and
|
||||
|
||||
In this case the select query was showing 95 results before the update
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -42,7 +42,7 @@ $ git checkout -b 55new 5_x-prod
|
||||
$ git reset --hard ilri/5_x-prod
|
||||
$ git rebase -i dspace-5.5
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ It looks like we might be able to use OUs now, instead of DCs:
|
||||
|
||||
$ ldapsearch -x -H ldaps://svcgroot2.cgiarad.org:3269/ -b "dc=cgiarad,dc=org" -D "admigration1@cgiarad.org" -W "(sAMAccountName=admigration1)"
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -42,7 +42,7 @@ I exported a random item’s metadata as CSV, deleted all columns except id
|
||||
|
||||
0000-0002-6115-0956||0000-0002-3812-8793||0000-0001-7462-405X
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ Add dc.type to the output options for Atmire’s Listings and Reports module
|
||||
Add dc.type to the output options for Atmire’s Listings and Reports module (#286)
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ I see thousands of them in the logs for the last few months, so it’s not r
|
||||
I’ve raised a ticket with Atmire to ask
|
||||
Another worrying error from dspace.log is:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -28,7 +28,7 @@ I checked to see if the Solr sharding task that is supposed to run on January 1s
|
||||
I tested on DSpace Test as well and it doesn’t work there either
|
||||
I asked on the dspace-tech mailing list because it seems to be broken, and actually now I’m not sure if we’ve ever had the sharding task run successfully over all these years
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -50,7 +50,7 @@ DELETE 1
|
||||
Create issue on GitHub to track the addition of CCAFS Phase II project tags (#301)
|
||||
Looks like we’ll be using cg.identifier.ccafsprojectpii as the field name
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -54,7 +54,7 @@ Interestingly, it seems DSpace 4.x’s thumbnails were sRGB, but forcing reg
|
||||
$ identify ~/Desktop/alc_contrastes_desafios.jpg
|
||||
/Users/aorth/Desktop/alc_contrastes_desafios.jpg JPEG 464x600 464x600+0+0 8-bit CMYK 168KB 0.000u 0:00.000
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -40,7 +40,7 @@ Testing the CMYK patch on a collection with 650 items:
|
||||
|
||||
$ [dspace]/bin/dspace filter-media -f -i 10568/16498 -p "ImageMagick PDF Thumbnail" -v >& /tmp/filter-media-cmyk.txt
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="May, 2017"/>
|
||||
<meta name="twitter:description" content="2017-05-01 ICARDA apparently started working on CG Core on their MEL repository They have done a few cg.* fields, but not very consistent and even copy some of CGSpace items: https://mel.cgiar.org/xmlui/handle/20.500.11766/6911?show=full https://cgspace.cgiar.org/handle/10568/73683 2017-05-02 Atmire got back about the Workflow Statistics issue, and apparently it’s a bug in the CUA module so they will send us a pull request 2017-05-04 Sync DSpace Test with database and assetstore from CGSpace Re-deploy DSpace Test with Atmire’s CUA patch for workflow statistics, run system updates, and restart the server Now I can see the workflow statistics and am able to select users, but everything returns 0 items Megan says there are still some mapped items are not appearing since last week, so I forced a full index-discovery -b Need to remember to check if the collection has more items (currently 39 on CGSpace, but 118 on the freshly reindexed DSPace Test) tomorrow: https://cgspace."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="June, 2017"/>
|
||||
<meta name="twitter:description" content="2017-06-01 After discussion with WLE and CGSpace content people, we decided to just add one metadata field for the WLE Research Themes The cg.identifier.wletheme field will be used for both Phase I and Phase II Research Themes Then we’ll create a new sub-community for Phase II and create collections for the research themes there The current “Research Themes” community will be renamed to “WLE Phase I Research Themes” Tagged all items in the current Phase I collections with their appropriate themes Create pull request to add Phase II research themes to the submission form: #328 Add cg."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ Merge changes for WLE Phase II theme rename (#329)
|
||||
Looking at extracting the metadata registries from ICARDA’s MEL DSpace database so we can compare fields with CGSpace
|
||||
We can use PostgreSQL’s extended output format (-x) plus sed to format the output into quasi XML:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -60,7 +60,7 @@ This was due to newline characters in the dc.description.abstract column, which
|
||||
I exported a new CSV from the collection on DSpace Test and then manually removed the characters in vim using g/^$/d
|
||||
Then I cleaned up the author authorities and HTML characters in OpenRefine and sent the file back to Abenet
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ Linode sent an alert that CGSpace (linode18) was using 261% CPU for the past two
|
||||
|
||||
Ask Sisay to clean up the WLE approvers a bit, as Marianne’s user account is both in the approvers step as well as the group
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ http://hdl.handle.net/10568/78495||http://hdl.handle.net/10568/79336
|
||||
There appears to be a pattern but I’ll have to look a bit closer and try to clean them up automatically, either in SQL or in OpenRefine
|
||||
Add Katherine Lutz to the groups for content submission and edit steps of the CGIAR System collections
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ Generate list of authors on CGSpace for Peter to go through and correct:
|
||||
dspace=# \copy (select distinct text_value, count(*) as count from metadatavalue where metadata_field_id = (select metadata_field_id from metadatafieldregistry where element = 'contributor' and qualifier = 'author') AND resource_type_id = 2 group by text_value order by count desc) to /tmp/authors.csv with csv;
|
||||
COPY 54701
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -30,7 +30,7 @@ The logs say “Timeout waiting for idle object”
|
||||
PostgreSQL activity says there are 115 connections currently
|
||||
The list of connections to XMLUI and REST API for today:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -150,7 +150,7 @@ dspace.log.2018-01-02:34
|
||||
|
||||
Danny wrote to ask for help renewing the wildcard ilri.org certificate and I advised that we should probably use Let’s Encrypt if it’s just a handful of domains
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -30,7 +30,7 @@ We don’t need to distinguish between internal and external works, so that
|
||||
Yesterday I figured out how to monitor DSpace sessions using JMX
|
||||
I copied the logic in the jmx_tomcat_dbpools provided by Ubuntu’s munin-plugins-java package and used the stuff I discovered about JMX in 2018-01
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -24,7 +24,7 @@ Export a CSV of the IITA community metadata for Martin Mueller
|
||||
|
||||
Export a CSV of the IITA community metadata for Martin Mueller
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ Catalina logs at least show some memory errors yesterday:
|
||||
I tried to test something on DSpace Test but noticed that it’s down since god knows when
|
||||
Catalina logs at least show some memory errors yesterday:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ http://localhost:3000/solr/statistics/update?stream.body=%3Ccommit/%3E
|
||||
Then I reduced the JVM heap size from 6144 back to 5120m
|
||||
Also, I switched it to use OpenJDK instead of Oracle Java, as well as re-worked the Ansible infrastructure scripts to support hosts choosing which distribution they want to use
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -58,7 +58,7 @@ real 74m42.646s
|
||||
user 8m5.056s
|
||||
sys 2m7.289s
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ During the mvn package stage on the 5.8 branch I kept getting issues with java r
|
||||
|
||||
There is insufficient memory for the Java Runtime Environment to continue.
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did
|
||||
The server only has 8GB of RAM so we’ll eventually need to upgrade to a larger one because we’ll start starving the OS, PostgreSQL, and command line batch processes
|
||||
I ran all system updates on DSpace Test and rebooted it
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -30,7 +30,7 @@ I’ll update the DSpace role in our Ansible infrastructure playbooks and ru
|
||||
Also, I’ll re-run the postgresql tasks because the custom PostgreSQL variables are dynamic according to the system’s RAM, and we never re-ran them after migrating to larger Linodes last month
|
||||
I’m testing the new DSpace 5.8 branch in my Ubuntu 18.04 environment and I’m getting those autowire errors in Tomcat 8.5.30 again:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ I created a GitHub issue to track this #389, because I’m super busy in Nai
|
||||
Phil Thornton got an ORCID identifier so we need to add it to the list on CGSpace and tag his existing items
|
||||
I created a GitHub issue to track this #389, because I’m super busy in Nairobi right now
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ Send a note about my dspace-statistics-api to the dspace-tech mailing list
|
||||
Linode has been sending mails a few times a day recently that CGSpace (linode18) has had high CPU usage
|
||||
Today these are the top 10 IPs:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ Then I ran all system updates and restarted the server
|
||||
|
||||
I noticed that there is another issue with PDF thumbnails on CGSpace, and I see there was another Ghostscript vulnerability last week
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -50,7 +50,7 @@ I don’t see anything interesting in the web server logs around that time t
|
||||
357 207.46.13.1
|
||||
903 54.70.40.11
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -72,7 +72,7 @@ real 0m19.873s
|
||||
user 0m22.203s
|
||||
sys 0m1.979s
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ Most worryingly, there are encoding errors in the abstracts for eleven items, fo
|
||||
|
||||
I think I will need to ask Udana to re-copy and paste the abstracts with more care using Google Docs
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -64,7 +64,7 @@ $ ./fix-metadata-values.py -i /tmp/2019-02-21-fix-4-regions.csv -db dspace -u ds
|
||||
$ ./delete-metadata-values.py -i /tmp/2019-02-21-delete-2-countries.csv -db dspace -u dspace -p 'fuuu' -m 228 -f cg.coverage.country -d
|
||||
$ ./delete-metadata-values.py -i /tmp/2019-02-21-delete-1-region.csv -db dspace -u dspace -p 'fuuu' -m 231 -f cg.coverage.region -d
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ DELETE 1
|
||||
|
||||
But after this I tried to delete the item from the XMLUI and it is still present…
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ Run system updates on CGSpace (linode18) and reboot it
|
||||
|
||||
Skype with Marie-Angélique and Abenet about CG Core v2
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ CGSpace
|
||||
|
||||
Abenet had another similar issue a few days ago when trying to find the stats for 2018 in the RTB community
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ After rebooting, all statistics cores were loaded… wow, that’s luck
|
||||
|
||||
Run system updates on DSpace Test (linode19) and reboot it
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -72,7 +72,7 @@ Here are the top ten IPs in the nginx XMLUI and REST/OAI logs this morning:
|
||||
7249 2a01:7e00::f03c:91ff:fe18:7396
|
||||
9124 45.5.186.2
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="October, 2019"/>
|
||||
<meta name="twitter:description" content="2019-10-01 Udana from IWMI asked me for a CSV export of their community on CGSpace I exported it, but a quick run through the csv-metadata-quality tool shows that there are some low-hanging fruits we can fix before I send him the data I will limit the scope to the titles, regions, subregions, and river basins for now to manually fix some non-breaking spaces (U+00A0) there that would otherwise be removed by the csv-metadata-quality script’s “unneccesary Unicode” fix: $ csvcut -c 'id,dc."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -58,7 +58,7 @@ Let’s see how many of the REST API requests were for bitstreams (because t
|
||||
# zcat --force /var/log/nginx/rest.log.*.gz | grep -E "[0-9]{1,2}/Oct/2019" | grep -c -E "/rest/bitstreams"
|
||||
106781
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ Make sure all packages are up to date and the package manager is up to date, the
|
||||
# dpkg -C
|
||||
# reboot
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -56,7 +56,7 @@ I tweeted the CGSpace repository link
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ The code finally builds and runs with a fresh install
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -42,7 +42,7 @@ You need to download this into the DSpace 6.x source and compile it
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ The third item now has a donut with score 1 since I tweeted it last week
|
||||
|
||||
On the same note, the one item Abenet pointed out last week now has a donut with score of 104 after I tweeted it last week
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ I see that CGSpace (linode18) is still using PostgreSQL JDBC driver version 42.2
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I sent Atmire the dspace.log from today and told them to log into the server to
|
||||
In other news, I checked the statistics API on DSpace 6 and it’s working
|
||||
I tried to build the OAI registry on the freshly migrated DSpace 6 on DSpace Test and I get an error:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ I restarted Tomcat and PostgreSQL and the issue was gone
|
||||
|
||||
Since I was restarting Tomcat anyways I decided to redeploy the latest changes from the 5_x-prod branch and I added a note about COVID-19 items to the CGSpace frontpage at Peter’s request
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ It is class based so I can easily add support for other vocabularies, and the te
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ I filed a bug on OpenRXV: https://github.com/ilri/OpenRXV/issues/39
|
||||
|
||||
I filed an issue on OpenRXV to make some minor edits to the admin UI: https://github.com/ilri/OpenRXV/issues/40
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -44,7 +44,7 @@ During the FlywayDB migration I got an error:
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ So far we’ve spent at least fifty hours to process the statistics and stat
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I started processing those (about 411,000 records):
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -50,7 +50,7 @@ For example, this item has 51 views on CGSpace, but 0 on AReS
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -60,7 +60,7 @@ $ curl -s 'http://localhost:9200/openrxv-items-temp/_count?q=*&pretty
|
||||
}
|
||||
}
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ Also, we found some issues building and running OpenRXV currently due to ecosyst
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -44,7 +44,7 @@ Perhaps one of the containers crashed, I should have looked closer but I was in
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I looked at the top user agents and IPs in the Solr statistics for last month an
|
||||
|
||||
I will add the RI/1.0 pattern to our DSpace agents overload and purge them from Solr (we had previously seen this agent with 9,000 hits or so in 2020-09), but I think I will leave the Microsoft Word one… as that’s an actual user…
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I simply started it and AReS was running again:
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -30,7 +30,7 @@ Export another list of ALL subjects on CGSpace, including AGROVOC and non-AGROVO
|
||||
localhost/dspace63= > \COPY (SELECT DISTINCT LOWER(text_value) AS subject, count(*) FROM metadatavalue WHERE dspace_object_id in (SELECT dspace_object_id FROM item) AND metadata_field_id IN (119, 120, 127, 122, 128, 125, 135, 203, 208, 210, 215, 123, 236, 242, 187) GROUP BY subject ORDER BY count DESC) to /tmp/2021-07-01-all-subjects.csv WITH CSV HEADER;
|
||||
COPY 20994
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ Update Docker images on AReS server (linode20) and reboot the server:
|
||||
|
||||
I decided to upgrade linode20 from Ubuntu 18.04 to 20.04
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ The syntax Moayad showed me last month doesn’t seem to honor the search qu
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ $ wc -l /tmp/2021-10-01-affiliations.txt
|
||||
|
||||
So we have 1879/7100 (26.46%) matching already
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ First I exported all the 2019 stats from CGSpace:
|
||||
$ ./run.sh -s http://localhost:8081/solr/statistics -f 'time:2019-*' -a export -o statistics-2019.json -k uid
|
||||
$ zstd statistics-2019.json
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -40,7 +40,7 @@ Purging 455 hits from WhatsApp in statistics
|
||||
|
||||
Total number of bot hits purged: 3679
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -24,7 +24,7 @@ Start a full harvest on AReS
|
||||
|
||||
Start a full harvest on AReS
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,7 @@ We agreed to try to do more alignment of affiliations/funders with ROR
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ $ ./ilri/check-duplicates.py -i /tmp/tac4.csv -db dspace -u dspace -p 'fuuu&
|
||||
$ csvcut -c id,filename ~/Downloads/2022-03-01-CGSpace-TAC-ICW-batch4-701-980.csv > /tmp/tac4-filenames.csv
|
||||
$ csvjoin -c id /tmp/2022-03-01-tac-batch4-701-980.csv /tmp/tac4-filenames.csv > /tmp/2022-03-01-tac-batch4-701-980-filenames.csv
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="April, 2022"/>
|
||||
<meta name="twitter:description" content="2022-04-01 I did G1GC tests on DSpace Test (linode26) to compliment the CMS tests I did yesterday The Discovery indexing took this long: real 334m33.625s user 227m51.331s sys 3m43.037s 2022-04-04 Start a full harvest on AReS Help Marianne with submit/approve access on a new collection on CGSpace Go back in Gaia’s batch reports to find records that she indicated for replacing on CGSpace (ie, those with better new copies, new versions, etc) Looking at the Solr statistics for 2022-03 on CGSpace I see 54."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -66,7 +66,7 @@ If I query Solr for time:2022-04* AND dns:*msnbot* AND dns:*.msn.com. I see a ha
|
||||
|
||||
I purged 93,974 hits from these IPs using my check-spider-ip-hits.sh script
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -48,7 +48,7 @@ There seem to be many more of these:
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ Also, the trgm functions I’ve used before are case insensitive, but Levens
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -24,7 +24,7 @@ Our request to add CC-BY-3.0-IGO to SPDX was approved a few weeks ago
|
||||
|
||||
Our request to add CC-BY-3.0-IGO to SPDX was approved a few weeks ago
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ I also fixed a few bugs and improved the region-matching logic
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I filed an issue to ask about Java 11+ support
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -44,7 +44,7 @@ I want to make sure they use groups instead of individuals where possible!
|
||||
|
||||
I reverted the Cocoon autosave change because it was more of a nuissance that Peter can’t upload CSVs from the web interface and is a very low severity security issue
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I exported the CCAFS and IITA communities, extracted just the country and region
|
||||
Add a few more authors to my CSV with author names and ORCID identifiers and tag 283 items!
|
||||
Replace “East Asia” with “Eastern Asia” region on CGSpace (UN M.49 region)
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ I see we have some new ones that aren’t in our list if I combine with this
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -32,7 +32,7 @@ I want to try to expand my use of their data to journals, publishers, volumes, i
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -28,7 +28,7 @@ Remove cg.subject.wle and cg.identifier.wletheme from CGSpace input form after c
|
||||
iso-codes 4.13.0 was released, which incorporates my changes to the common names for Iran, Laos, and Syria
|
||||
I finally got through with porting the input form from DSpace 6 to DSpace 7
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ I also did a check for missing country/region mappings with csv-metadata-quality
|
||||
|
||||
Start a harvest on AReS
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -46,7 +46,7 @@ Also I found at least two spelling mistakes, for example “decison support
|
||||
|
||||
Work on cleaning, proofing, and uploading twenty-seven records for IFPRI to CGSpace
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -44,7 +44,7 @@ From what I can see we need to upgrade the MODS schema from 3.1 to 3.7 and then
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="July, 2023"/>
|
||||
<meta name="twitter:description" content="2023-07-01 Export CGSpace to check for missing Initiative collection mappings Start harvesting on AReS 2023-07-02 Minor edits to the crossref_doi_lookup.py script while running some checks from 22,000 CGSpace DOIs 2023-07-03 I analyzed the licenses declared by Crossref and found with high confidence that ~400 of ours were incorrect I took the more accurate ones from Crossref and updated the items on CGSpace I took a few hundred ISBNs as well for where we were missing them I also tagged ~4,700 items with missing licenses as “Copyrighted; all rights reserved” based on their Crossref license status being TDM, mostly from Elsevier, Wiley, and Springer Checking a dozen or so manually, I confirmed that if Crossref only has a TDM license then it’s usually copyrighted (could still be open access, but we can’t tell via Crossref) I would be curious to write a script to check the Unpaywall API for open access status… In the past I found that their license status was not very accurate, but the open access status might be more reliable More minor work on the DSpace 7 item views I learned some new Angular template syntax I created a custom component to show Creative Commons licenses on the simple item page I also decided that I don’t like the Impact Area icons as a component because they don’t have any visual meaning 2023-07-04 Focus group meeting with CGSpace partners about DSpace 7 I added a themed file selection component to the CGSpace theme It displays the bistream description instead of the file name, just like we did in DSpace 6 XMLUI I added a custom component to show share icons 2023-07-05 I spent some time trying to update OpenRXV from Angular 9 to 10 to 11 to 12 to 13 Most things work but there are some minor bugs it seems Mishell from CIP emailed me to say she was having problems approving an item on CGSpace Looking at PostgreSQL I saw there were a dozen or so locks that were several hours and even over one day old so I killed those processes and told her to try again 2023-07-06 Types meeting I wrote a Python script to check Unpaywall for some information about DOIs 2023-07-7 Continue exploring Unpaywall data for some of our DOIs In the past I’ve found their licensing information to not be very reliable (preferring Crossref), but I think their open access status is more reliable, especially when the provider is listed as being the publisher Even so, sometimes the version can be “acceptedVersion”, which is presumably the author’s version, as opposed to the “publishedVersion”, which means it’s available as open access on the publisher’s website I did some quality assurance and found ~100 that were marked as Limited Access, but should have been Open Access, and fixed a handful of licenses Delete duplicate metadata as described in my DSpace issue from last year: https://github."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -34,7 +34,7 @@ I did some minor cleanups myself and applied them to CGSpace
|
||||
|
||||
Start working on some batch uploads for IFPRI
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ Start a harvest on AReS
|
||||
Export CGSpace to check for missing Initiative collection mappings
|
||||
Start a harvest on AReS
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ We can be on the safe side by using only abstracts for items that are licensed u
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -42,7 +42,7 @@ I improved the filtering and wrote some Python using pandas to merge my sources
|
||||
Export CGSpace to check missing Initiative collection mappings
|
||||
Start a harvest on AReS
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -18,7 +18,7 @@
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="December, 2023"/>
|
||||
<meta name="twitter:description" content="2023-12-01 There is still high load on CGSpace and I don’t know why I don’t see a high number of sessions compared to previous days in the last few weeks $ for file in dspace.log.2023-11-[23]*; do echo "$file"; grep -a -oE 'session_id=[A-Z0-9]{32}' "$file" | sort | uniq | wc -l; done dspace.log.2023-11-20 22865 dspace.log.2023-11-21 20296 dspace.log.2023-11-22 19688 dspace.log.2023-11-23 17906 dspace.log.2023-11-24 18453 dspace.log.2023-11-25 17513 dspace.log.2023-11-26 19037 dspace.log.2023-11-27 21103 dspace.log.2023-11-28 23023 dspace.log.2023-11-29 23545 dspace."/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
@ -40,7 +40,7 @@ I sent the bundle to the Handle admins to make sure it’s OK before we do t
|
||||
Continue testing and debugging the cgspace-java-helpers on DSpace 7
|
||||
Work on IFPRI ISNAR archive cleanup
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.128.2">
|
||||
<meta name="generator" content="Hugo 0.131.0">
|
||||
|
||||
|
||||
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user