Add notes for 2019-12-22

2024-11-25 16:08:19 +01:00 · 2019-12-22 12:14:25 +02:00 · 2019-12-22 12:14:25 +02:00 · 838dea0210
commit 838dea0210
parent 2ea64137a2
4 changed files with 80 additions and 18 deletions
--- 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
+
 <!-- vim: set sw=2 ts=2: -->
--- 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
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-12/" />
 <meta property="article:published_time" content="2019-12-01T11:22:30+02:00" />
-<meta property="article:modified_time" content="2019-12-18T19:05:09+02:00" />
+<meta property="article:modified_time" content="2019-12-18T22:03:36+02:00" />

 <meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="December, 2019"/>
@ -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
 </ul>
 </li>
 </ul>
+<h2 id="2019-12-22">2019-12-22</h2>
+<ul>
+<li>I ran the <code>dspace cleanup</code> process on CGSpace (linode18) and had an error:</li>
+</ul>
+<pre><code>Error: ERROR: update or delete on table &quot;bitstream&quot; violates foreign key constraint &quot;bundle_primary_bitstream_id_fkey&quot; on table &quot;bundle&quot;
+  Detail: Key (bitstream_id)=(179441) is still referenced from table &quot;bundle&quot;.
+</code></pre><ul>
+<li>The solution is to delete that bitstream manually:</li>
+</ul>
+<pre><code>$ psql dspace -c 'update bundle set primary_bitstream_id=NULL where primary_bitstream_id in (179441);'
+UPDATE 1
+</code></pre><ul>
+<li>Adjust <a href="/cgspace-notes/cgspace-cgcorev2-migration/">CG Core v2 migrataion notes</a> to use <code>cg.review-status</code> instead of <code>cg.peer-reviewed</code>
+<ul>
+<li>I had <a href="https://github.com/AgriculturalSemantics/cg-core/issues/14">raised the issue</a> with Marie-Angelique earlier this month</li>
+<li>It makes much more sense to use a wider scope here than a simple boolean</li>
+</ul>
+</li>
+<li>I also noticed another field that we should be using in DCTERMS instead of CG: <code>cg.targetaudience</code>
+<ul>
+<li><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/2012-06-14/?v=terms#audience">DCTERMS says that <code>dcterms.audience</code> should be used to describe a A class of entity for whom the resource is intended or useful.&quot;</a></li>
+<li>I will update my notes for this so that we use that field instead</li>
+<li>I don't see &ldquo;audience&rdquo; on the <a href="https://github.com/AgriculturalSemantics/cg-core/">cg-core</a> repository so I filed <a href="https://github.com/AgriculturalSemantics/cg-core/issues/19">an issue</a> to raise it with Marie-Angelique</li>
+</ul>
+</li>
+</ul>
 <!-- raw HTML omitted -->

  
--- a/docs/cgspace-cgcorev2-migration/index.html
+++ b/docs/cgspace-cgcorev2-migration/index.html
@ -10,7 +10,7 @@
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/cgspace-cgcorev2-migration/" />
 <meta property="article:published_time" content="2019-10-28T13:27:35+02:00" />
-<meta property="article:modified_time" content="2019-11-17T15:39:10+02:00" />
+<meta property="article:modified_time" content="2019-12-22T11:56:45+02:00" />

 <meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="CGSpace CG Core v2 Migration"/>
@ -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 @@
 <li><a href="#implementation-progress">Implementation Progress</a></li>
 </ul>
 <h2 id="proposed-changes">Proposed Changes</h2>
-<p>As of 2019-11-17 the scope of the changes includes the following fields:</p>
+<p>As of 2019-12-22 the scope of the changes includes the following fields:</p>
 <ul>
 <li>cg.creator.id→cg.creator.identifier
 <ul>
@ -124,7 +124,7 @@
 <li>values from CrossRef or Grid.ac if possible</li>
 </ul>
 </li>
-<li>dc.description.version→cg.peer-reviewed</li>
+<li>dc.description.version→cg.review-status</li>
 <li>cg.fulltextstatus→cg.howpublished
 <ul>
 <li>CGSpace uses values like &ldquo;Formally Published&rdquo; or &ldquo;Grey Literature&rdquo;</li>
@ -156,6 +156,7 @@
 <li>dc.type→dcterms.type</li>
 <li>dc.identifier.isbn→cg.isbn</li>
 <li>dc.identifier.issn→cg.issn</li>
+<li>cg.targetaudience→dcterms.audience</li>
 </ul>
 <p>The following fields are currently out of the scope of this migration because they are used internally by DSpace 5.x/6.x and would be difficult to change without significant modifications to the core of the code:</p>
 <ul>
@ -172,7 +173,7 @@
 <ul>
 <li><input checked="" disabled="" type="checkbox">cg.creator.identifier (242)</li>
 <li><input checked="" disabled="" type="checkbox">cg.contributor.donor (243)</li>
-<li><input checked="" disabled="" type="checkbox">cg.peer-reviewed (244)</li>
+<li><input checked="" disabled="" type="checkbox">cg.review-status (244)</li>
 <li><input checked="" disabled="" type="checkbox">cg.howpublished (245)</li>
 <li><input checked="" disabled="" type="checkbox">cg.journal (246)</li>
 <li><input checked="" disabled="" type="checkbox">cg.isbn (247)</li>
@ -185,6 +186,7 @@
 <li><input disabled="" type="checkbox">cg.fulltextstatus</li>
 <li><input disabled="" type="checkbox">cg.identifier.status</li>
 <li><input disabled="" type="checkbox">cg.link.reference</li>
+<li><input disabled="" type="checkbox">cg.targetaudience</li>
 </ul>
 <h2 id="implementation-progress">Implementation Progress</h2>
 <p>Tally of the status of the implementation of the new fields in the CGSpace <code>5_x-cgcorev2</code> branch.</p>
@ -263,7 +265,7 @@
 <td align="center"></td>
 </tr>
 <tr>
-<td>cg.peer-reviewed</td>
+<td>cg.review-status</td>
 <td align="center">✓</td>
 <td align="center">✓</td>
 <td align="center">✓</td>
@ -402,6 +404,16 @@
 <td align="center">✓</td>
 <td align="center"></td>
 </tr>
+<tr>
+<td>dcterms.audience</td>
+<td align="center">✓</td>
+<td align="center">✓</td>
+<td align="center">-</td>
+<td align="center">-</td>
+<td align="center">-</td>
+<td align="center">✓</td>
+<td align="center"></td>
+</tr>
 </tbody>
 </table>
 <p>There are a few things that I need to check once I get a deployment of this code up and running:</p>
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@ -4,27 +4,27 @@
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/categories/</loc>
-    <lastmod>2019-12-18T19:05:09+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2019-12-18T19:05:09+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/2019-12/</loc>
-    <lastmod>2019-12-18T19:05:09+02:00</lastmod>
+    <lastmod>2019-12-18T22:03:36+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/categories/notes/</loc>
-    <lastmod>2019-12-18T19:05:09+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
-    <lastmod>2019-12-18T19:05:09+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
@ -34,17 +34,17 @@
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/cgspace-cgcorev2-migration/</loc>
-    <lastmod>2019-11-17T15:39:10+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/tags/migration/</loc>
-    <lastmod>2019-11-17T15:39:10+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>
    <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
-    <lastmod>2019-11-17T15:39:10+02:00</lastmod>
+    <lastmod>2019-12-22T11:56:45+02:00</lastmod>
  </url>
  
  <url>