From 838dea0210a132f2890590d5fe6467f1390a3950 Mon Sep 17 00:00:00 2001 From: Alan Orth Date: Sun, 22 Dec 2019 12:14:25 +0200 Subject: [PATCH] Add notes for 2019-12-22 --- content/posts/2019-12.md | 24 ++++++++++++++++ docs/2019-12/index.html | 32 ++++++++++++++++++++-- docs/cgspace-cgcorev2-migration/index.html | 26 +++++++++++++----- docs/sitemap.xml | 16 +++++------ 4 files changed, 80 insertions(+), 18 deletions(-) diff --git a/content/posts/2019-12.md b/content/posts/2019-12.md index ee5f30146..f8c1327df 100644 --- a/content/posts/2019-12.md +++ b/content/posts/2019-12.md @@ -181,4 +181,28 @@ UPDATE 2 - The DOI has an Altmetric score of 259, but for the Handle it is HTTP 404! - I emailed Altmetric support +## 2019-12-22 + +- I ran the `dspace cleanup` process on CGSpace (linode18) and had an error: + +``` +Error: ERROR: update or delete on table "bitstream" violates foreign key constraint "bundle_primary_bitstream_id_fkey" on table "bundle" + Detail: Key (bitstream_id)=(179441) is still referenced from table "bundle". +``` + +- The solution is to delete that bitstream manually: + +``` +$ psql dspace -c 'update bundle set primary_bitstream_id=NULL where primary_bitstream_id in (179441);' +UPDATE 1 +``` + +- Adjust [CG Core v2 migrataion notes]({{< relref "cgspace-cgcorev2-migration.md" >}}) to use `cg.review-status` instead of `cg.peer-reviewed` + - I had [raised the issue](https://github.com/AgriculturalSemantics/cg-core/issues/14) with Marie-Angelique earlier this month + - It makes much more sense to use a wider scope here than a simple boolean +- I also noticed another field that we should be using in DCTERMS instead of CG: `cg.targetaudience` + - [DCTERMS says that `dcterms.audience` should be used to describe a A class of entity for whom the resource is intended or useful."](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/2012-06-14/?v=terms#audience) + - I will update my notes for this so that we use that field instead + - I don't see "audience" on the [cg-core](https://github.com/AgriculturalSemantics/cg-core/) repository so I filed [an issue](https://github.com/AgriculturalSemantics/cg-core/issues/19) to raise it with Marie-Angelique + diff --git a/docs/2019-12/index.html b/docs/2019-12/index.html index 3a68e70f4..f8f4a7140 100644 --- a/docs/2019-12/index.html +++ b/docs/2019-12/index.html @@ -24,7 +24,7 @@ Make sure all packages are up to date and the package manager is up to date, the - + @@ -53,9 +53,9 @@ Make sure all packages are up to date and the package manager is up to date, the "@type": "BlogPosting", "headline": "December, 2019", "url": "https:\/\/alanorth.github.io\/cgspace-notes\/2019-12\/", - "wordCount": "1219", + "wordCount": "1387", "datePublished": "2019-12-01T11:22:30+02:00", - "dateModified": "2019-12-18T19:05:09+02:00", + "dateModified": "2019-12-18T22:03:36+02:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -326,6 +326,32 @@ UPDATE 2 +

2019-12-22

+ +
Error: ERROR: update or delete on table "bitstream" violates foreign key constraint "bundle_primary_bitstream_id_fkey" on table "bundle"
+  Detail: Key (bitstream_id)=(179441) is still referenced from table "bundle".
+
+
$ psql dspace -c 'update bundle set primary_bitstream_id=NULL where primary_bitstream_id in (179441);'
+UPDATE 1
+
diff --git a/docs/cgspace-cgcorev2-migration/index.html b/docs/cgspace-cgcorev2-migration/index.html index dae61438c..bf7f7f13e 100644 --- a/docs/cgspace-cgcorev2-migration/index.html +++ b/docs/cgspace-cgcorev2-migration/index.html @@ -10,7 +10,7 @@ - + @@ -25,9 +25,9 @@ "@type": "BlogPosting", "headline": "CGSpace CG Core v2 Migration", "url": "https:\/\/alanorth.github.io\/cgspace-notes\/cgspace-cgcorev2-migration\/", - "wordCount": "546", + "wordCount": "555", "datePublished": "2019-10-28T13:27:35+02:00", - "dateModified": "2019-11-17T15:39:10+02:00", + "dateModified": "2019-12-22T11:56:45+02:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -108,7 +108,7 @@
  • Implementation Progress

    • Proposed Changes

    -

    As of 2019-11-17 the scope of the changes includes the following fields:

    +

    As of 2019-12-22 the scope of the changes includes the following fields: