Update notes for 2019-01-24

This commit is contained in:
Alan Orth 2019-01-24 16:25:16 +02:00
parent 7af7135a91
commit df8102b00b
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 19 additions and 8 deletions

View File

@ -894,5 +894,9 @@ identify: CorruptImageProfile `xmp' @ warning/profile.c/SetImageProfileInternal/
- CIAT's community currently has 12,000 items in it so this is normal - CIAT's community currently has 12,000 items in it so this is normal
- The issue with goo.gl links that we saw yesterday appears to be resolved, as links are working again... - The issue with goo.gl links that we saw yesterday appears to be resolved, as links are working again...
- For example: https://goo.gl/fb/VRj9Gq - For example: https://goo.gl/fb/VRj9Gq
- The full [list of MARC Relators on the Library of Congress website](http://id.loc.gov/vocabulary/relators.html) linked from the [DMCI relators page](http://dublincore.org/usage/documents/relators/) is very confusing
- Looking at the default DSpace XMLUI crosswalk in [xhtml-head-item.properties](https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/crosswalks/xhtml-head-item.properties) I see a very complete mapping of DSpace DC and QDC fields to DCTERMS
- This is good for standards-compliant web crawlers, but what about for those harvesting via REST or OAI APIs?
- I sent a message titled "[DC, QDC, and DCTERMS: reviewing our metadata practices](https://groups.google.com/forum/#!topic/dspace-tech/phV_t51TGuE)" to the dspace-tech mailing list to ask about some of this
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

View File

@ -27,7 +27,7 @@ I don&rsquo;t see anything interesting in the web server logs around that time t
" /> " />
<meta property="og:type" content="article" /> <meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-01/" /><meta property="article:published_time" content="2019-01-02T09:48:30&#43;02:00"/> <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-01/" /><meta property="article:published_time" content="2019-01-02T09:48:30&#43;02:00"/>
<meta property="article:modified_time" content="2019-01-24T10:59:03&#43;02:00"/> <meta property="article:modified_time" content="2019-01-24T13:14:42&#43;02:00"/>
<meta name="twitter:card" content="summary"/> <meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="January, 2019"/> <meta name="twitter:title" content="January, 2019"/>
@ -60,9 +60,9 @@ I don&rsquo;t see anything interesting in the web server logs around that time t
"@type": "BlogPosting", "@type": "BlogPosting",
"headline": "January, 2019", "headline": "January, 2019",
"url": "https://alanorth.github.io/cgspace-notes/2019-01/", "url": "https://alanorth.github.io/cgspace-notes/2019-01/",
"wordCount": "4561", "wordCount": "4647",
"datePublished": "2019-01-02T09:48:30&#43;02:00", "datePublished": "2019-01-02T09:48:30&#43;02:00",
"dateModified": "2019-01-24T10:59:03&#43;02:00", "dateModified": "2019-01-24T13:14:42&#43;02:00",
"author": { "author": {
"@type": "Person", "@type": "Person",
"name": "Alan Orth" "name": "Alan Orth"
@ -1186,6 +1186,13 @@ identify: CorruptImageProfile `xmp' @ warning/profile.c/SetImageProfileInternal/
<li>CIAT&rsquo;s community currently has 12,000 items in it so this is normal</li> <li>CIAT&rsquo;s community currently has 12,000 items in it so this is normal</li>
<li>The issue with goo.gl links that we saw yesterday appears to be resolved, as links are working again&hellip;</li> <li>The issue with goo.gl links that we saw yesterday appears to be resolved, as links are working again&hellip;</li>
<li>For example: <a href="https://goo.gl/fb/VRj9Gq">https://goo.gl/fb/VRj9Gq</a></li> <li>For example: <a href="https://goo.gl/fb/VRj9Gq">https://goo.gl/fb/VRj9Gq</a></li>
<li>The full <a href="http://id.loc.gov/vocabulary/relators.html">list of MARC Relators on the Library of Congress website</a> linked from the <a href="http://dublincore.org/usage/documents/relators/">DMCI relators page</a> is very confusing</li>
<li>Looking at the default DSpace XMLUI crosswalk in <a href="https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/crosswalks/xhtml-head-item.properties">xhtml-head-item.properties</a> I see a very complete mapping of DSpace DC and QDC fields to DCTERMS
<ul>
<li>This is good for standards-compliant web crawlers, but what about for those harvesting via REST or OAI APIs?</li>
</ul></li>
<li>I sent a message titled &ldquo;<a href="https://groups.google.com/forum/#!topic/dspace-tech/phV_t51TGuE">DC, QDC, and DCTERMS: reviewing our metadata practices</a>&rdquo; to the dspace-tech mailing list to ask about some of this</li>
</ul> </ul>
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

View File

@ -4,7 +4,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/2019-01/</loc> <loc>https://alanorth.github.io/cgspace-notes/2019-01/</loc>
<lastmod>2019-01-24T10:59:03+02:00</lastmod> <lastmod>2019-01-24T13:14:42+02:00</lastmod>
</url> </url>
<url> <url>
@ -204,7 +204,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2019-01-24T10:59:03+02:00</lastmod> <lastmod>2019-01-24T13:14:42+02:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -215,7 +215,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2019-01-24T10:59:03+02:00</lastmod> <lastmod>2019-01-24T13:14:42+02:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -227,13 +227,13 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc> <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2019-01-24T10:59:03+02:00</lastmod> <lastmod>2019-01-24T13:14:42+02:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2019-01-24T10:59:03+02:00</lastmod> <lastmod>2019-01-24T13:14:42+02:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>