alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2023-10-05

Browse Source
This commit is contained in:
Alan Orth
2023-10-05 17:58:03 +03:00
parent cb40610726
commit 62838a091c
33 changed files with 59 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/2023-10/index.html
View File

@ -20,7 +20,7 @@ We can be on the safe side by using only abstracts for items that are licensed u
<meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2023-10/" />
<meta property="article:published_time" content="2023-10-02T09:05:36+03:00" />
<meta property="article:modified_time" content="2023-10-02T09:05:36+03:00" />
<meta property="article:modified_time" content="2023-10-04T09:24:33+03:00" />
@ -46,9 +46,9 @@ We can be on the safe side by using only abstracts for items that are licensed u
"@type": "BlogPosting",
"headline": "October, 2023",
"url": "https://alanorth.github.io/cgspace-notes/2023-10/",
"wordCount": "286",
"wordCount": "417",
"datePublished": "2023-10-02T09:05:36+03:00",
"dateModified": "2023-10-02T09:05:36+03:00",
"dateModified": "2023-10-04T09:24:33+03:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -165,6 +165,17 @@ We can be on the safe side by using only abstracts for items that are licensed u
</li>
<li>Submit <a href="https://github.com/DSpace/DSpace/issues/9104">an issue regarding duplicate Discovery sort fields</a> in DSpace 7</li>
</ul>
<h2 id="2023-10-05">2023-10-05</h2>
<ul>
<li>Some discussion this week about issue and online dates for journal articles, with regards to PRMS
<ul>
<li>I looked more closely at the <a href="https://github.com/CrossRef/rest-api-doc/blob/master/api_format.md">Crossref API docs</a> and realized (again) that their &ldquo;issue&rdquo; date is not the same as our issue date—they take the earlier of the print and online dates!</li>
<li>Also, <em>very many</em> items have no print date at all, perhaps due to delays, errors, or simply because the journal is &ldquo;online only&rdquo;!</li>
<li>I suggested again that PRMS should consider both, and take the earlier of the two, then make sure whether the date is in the current reporting period</li>
<li>I managed to find 80 items with print publishing dates from 2023 and updated those from Crossref, but for the rest we will have to think about how we handle them</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->