mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-10 17:15:46 +01:00
Update notes for 2017-03-07
This commit is contained in:
parent
ccaace3a37
commit
782e34b02c
@ -132,4 +132,4 @@ google.citation_doi = cg.identifier.doi
|
||||
- Only items imported manually can have the other handles
|
||||
- I need to talk to Michael and Peter to share the news, and discuss the structure of their community(s) and try some actual test data
|
||||
- We'll need to do some data cleaning to make sure they are using the same fields we are, like `dc.type` and `cg.identifier.status`
|
||||
- Another thing is that the import process creates new `dc.date.accessioned` and `dc.date.available` fields, so we end up with duplicates
|
||||
- Another thing is that the import process creates new `dc.date.accessioned` and `dc.date.available` fields, so we end up with duplicates (is it important to preserve the originals for these?)
|
||||
|
@ -37,7 +37,7 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
|
||||
|
||||
|
||||
<meta property="article:published_time" content="2017-03-01T17:08:52+02:00"/>
|
||||
<meta property="article:modified_time" content="2017-03-07T14:03:29+02:00"/>
|
||||
<meta property="article:modified_time" content="2017-03-07T18:01:24+02:00"/>
|
||||
|
||||
|
||||
|
||||
@ -94,13 +94,13 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
|
||||
|
||||
"headline": "March, 2017",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2017-03/",
|
||||
"wordCount": "881",
|
||||
"wordCount": "890",
|
||||
|
||||
|
||||
"datePublished": "2017-03-01T17:08:52+02:00",
|
||||
|
||||
|
||||
"dateModified": "2017-03-07T14:03:29+02:00",
|
||||
"dateModified": "2017-03-07T18:01:24+02:00",
|
||||
|
||||
|
||||
"author": {
|
||||
@ -321,7 +321,7 @@ DirectClass sRGB Alpha
|
||||
</ul></li>
|
||||
<li>I need to talk to Michael and Peter to share the news, and discuss the structure of their community(s) and try some actual test data</li>
|
||||
<li>We’ll need to do some data cleaning to make sure they are using the same fields we are, like <code>dc.type</code> and <code>cg.identifier.status</code></li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates</li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates (is it important to preserve the originals for these?)</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
@ -167,7 +167,7 @@ DirectClass sRGB Alpha
|
||||
</ul></li>
|
||||
<li>I need to talk to Michael and Peter to share the news, and discuss the structure of their community(s) and try some actual test data</li>
|
||||
<li>We&rsquo;ll need to do some data cleaning to make sure they are using the same fields we are, like <code>dc.type</code> and <code>cg.identifier.status</code></li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates</li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates (is it important to preserve the originals for these?)</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
|
@ -167,7 +167,7 @@ DirectClass sRGB Alpha
|
||||
</ul></li>
|
||||
<li>I need to talk to Michael and Peter to share the news, and discuss the structure of their community(s) and try some actual test data</li>
|
||||
<li>We&rsquo;ll need to do some data cleaning to make sure they are using the same fields we are, like <code>dc.type</code> and <code>cg.identifier.status</code></li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates</li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates (is it important to preserve the originals for these?)</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
|
@ -3,7 +3,7 @@
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/2017-03/</loc>
|
||||
<lastmod>2017-03-07T14:03:29+02:00</lastmod>
|
||||
<lastmod>2017-03-07T18:01:24+02:00</lastmod>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
@ -88,19 +88,19 @@
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/</loc>
|
||||
<lastmod>2017-03-07T14:03:29+02:00</lastmod>
|
||||
<lastmod>2017-03-07T18:01:24+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
|
||||
<lastmod>2017-03-07T14:03:29+02:00</lastmod>
|
||||
<lastmod>2017-03-07T18:01:24+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/post/</loc>
|
||||
<lastmod>2017-03-07T14:03:29+02:00</lastmod>
|
||||
<lastmod>2017-03-07T18:01:24+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
|
@ -166,7 +166,7 @@ DirectClass sRGB Alpha
|
||||
</ul></li>
|
||||
<li>I need to talk to Michael and Peter to share the news, and discuss the structure of their community(s) and try some actual test data</li>
|
||||
<li>We&rsquo;ll need to do some data cleaning to make sure they are using the same fields we are, like <code>dc.type</code> and <code>cg.identifier.status</code></li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates</li>
|
||||
<li>Another thing is that the import process creates new <code>dc.date.accessioned</code> and <code>dc.date.available</code> fields, so we end up with duplicates (is it important to preserve the originals for these?)</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user