Update theme and regenerate

This commit is contained in:
Alan Orth 2017-01-10 15:25:11 +02:00
parent 5545aa5ca6
commit b580f14896
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
27 changed files with 40 additions and 49 deletions

View File

@ -98,3 +98,8 @@ Caused by: java.net.SocketException: Broken pipe (Write failed)
- She said she only mapped it once, but it appears to be mapped 184 times
![Crazy item mapping](/cgspace-notes/2017/01/mapping-crazy-duplicate.png)
## 2017-01-10
- I tried to clean up the duplicate mappings by exporting the item's metadata to CSV, editing, and re-importing, but DSpace said "no changes were detected"
- I've asked on the dspace-tech mailing list to see if anyone can help

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="November, 2015" />
<meta property="og:description" content="2015-11-22

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="December, 2015" />
<meta property="og:description" content="2015-12-02

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="January, 2016" />
<meta property="og:description" content="2016-01-13

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="February, 2016" />
<meta property="og:description" content="2016-02-05

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="March, 2016" />
<meta property="og:description" content="2016-03-02

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="April, 2016" />
<meta property="og:description" content="2016-04-04

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="May, 2016" />
<meta property="og:description" content="2016-05-01

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="June, 2016" />
<meta property="og:description" content="2016-06-01

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="July, 2016" />
<meta property="og:description" content="2016-07-01

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="August, 2016" />
<meta property="og:description" content="2016-08-01

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="September, 2016" />
<meta property="og:description" content="2016-09-01

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="October, 2016" />
<meta property="og:description" content="2016-10-03 Testing adding ORCIDs to a CSV file for a single item to see if the author orders get messed up Need to test the following scenarios to see how author order is affected: ORCIDs only ORCIDs plus normal authors I exported a random item&rsquo;s metadata as CSV, deleted all columns except id and collection, and made a new coloum called ORCID:dc.contributor.author with the following random ORCIDs from the ORCID registry: 0000-0002-6115-0956||0000-0002-3812-8793||0000-0001-7462-405X Hmm, with the dc." />

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="November, 2016" />
<meta property="og:description" content="2016-11-01 Add dc.type to the output options for Atmire&rsquo;s Listings and Reports module (#286) 2016-11-02 Migrate DSpace Test to DSpace 5.5 (notes) Run all updates on DSpace Test and reboot the server Looks like the OAI bug from DSpace 5.1 that caused validation at Base Search to fail is now fixed and DSpace Test passes validation! (#63) Indexing Discovery on DSpace Test took 332 minutes, which is like five times as long as it usually takes At the end it appeared to finish correctly but there were lots of errors right after it finished: 2016-11-02 15:09:48,578 INFO com." />

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="December, 2016" />
<meta property="og:description" content="2016-12-02 CGSpace was down for five hours in the morning while I was sleeping While looking in the logs for errors, I see tons of warnings about Atmire MQM: 2016-12-02 03:00:32,352 WARN com.atmire.metadataquality.batchedit.BatchEditConsumer @ BatchEditConsumer should not have been given this kind of Subject in an event, skipping: org.dspace.event.Event(eventType=CREATE, SubjectType=BUNDLE, SubjectID=70316, ObjectType=(Unknown), ObjectID=-1, TimeStamp=1480647632305, dispatcher=1544803905, detail=[null], transactionID=&quot;TX157907838689377964651674089851855413607&quot;) 2016-12-02 03:00:32,353 WARN com.atmire.metadataquality.batchedit.BatchEditConsumer @ BatchEditConsumer should not have been given this kind of Subject in an event, skipping: org." />

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="January, 2017" />
<meta property="og:description" content="2017-01-02 I checked to see if the Solr sharding task that is supposed to run on January 1st had run and saw there was an error I tested on DSpace Test as well and it doesn&rsquo;t work there either I asked on the dspace-tech mailing list because it seems to be broken, and actually now I&rsquo;m not sure if we&rsquo;ve ever had the sharding task run successfully over all these years 2017-01-04 I tried to shard my local dev instance and it fails the same way: $ JAVA_OPTS=&quot;-Xms768m -Xmx768m -Dfile." />
@ -30,7 +28,7 @@
<meta itemprop="dateModified" content="2017-01-02T10:43:00&#43;03:00" />
<meta itemprop="wordCount" content="453">
<meta itemprop="wordCount" content="492">
@ -217,6 +215,13 @@ Caused by: java.net.SocketException: Broken pipe (Write failed)
<p><img src="/cgspace-notes/2017/01/mapping-crazy-duplicate.png" alt="Crazy item mapping" /></p>
<h2 id="2017-01-10">2017-01-10</h2>
<ul>
<li>I tried to clean up the duplicate mappings by exporting the item&rsquo;s metadata to CSV, editing, and re-importing, but DSpace said &ldquo;no changes were detected&rdquo;</li>
<li>I&rsquo;ve asked on the dspace-tech mailing list to see if anyone can help</li>
</ul>

File diff suppressed because one or more lines are too long

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="CGSpace Notes" />
<meta property="og:description" content="" />

View File

@ -121,6 +121,13 @@ Caused by: java.net.SocketException: Broken pipe (Write failed)
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&#34;https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/01/mapping-crazy-duplicate.png&#34; alt=&#34;Crazy item mapping&#34; /&gt;&lt;/p&gt;
&lt;h2 id=&#34;2017-01-10&#34;&gt;2017-01-10&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I tried to clean up the duplicate mappings by exporting the item&amp;rsquo;s metadata to CSV, editing, and re-importing, but DSpace said &amp;ldquo;no changes were detected&amp;rdquo;&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;ve asked on the dspace-tech mailing list to see if anyone can help&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="CGSpace Notes" />
<meta property="og:description" content="" />

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="Posts" />
<meta property="og:description" content="" />

View File

@ -121,6 +121,13 @@ Caused by: java.net.SocketException: Broken pipe (Write failed)
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&#34;https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/01/mapping-crazy-duplicate.png&#34; alt=&#34;Crazy item mapping&#34; /&gt;&lt;/p&gt;
&lt;h2 id=&#34;2017-01-10&#34;&gt;2017-01-10&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I tried to clean up the duplicate mappings by exporting the item&amp;rsquo;s metadata to CSV, editing, and re-importing, but DSpace said &amp;ldquo;no changes were detected&amp;rdquo;&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;ve asked on the dspace-tech mailing list to see if anyone can help&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="Posts" />
<meta property="og:description" content="" />

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="Notes" />
<meta property="og:description" content="" />

View File

@ -120,6 +120,13 @@ Caused by: java.net.SocketException: Broken pipe (Write failed)
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&#34;https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/01/mapping-crazy-duplicate.png&#34; alt=&#34;Crazy item mapping&#34; /&gt;&lt;/p&gt;
&lt;h2 id=&#34;2017-01-10&#34;&gt;2017-01-10&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I tried to clean up the duplicate mappings by exporting the item&amp;rsquo;s metadata to CSV, editing, and re-importing, but DSpace said &amp;ldquo;no changes were detected&amp;rdquo;&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;ve asked on the dspace-tech mailing list to see if anyone can help&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

View File

@ -3,9 +3,7 @@
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta property="og:title" content="Notes" />
<meta property="og:description" content="" />

@ -1 +1 @@
Subproject commit 0c264bb4215741108ebb0299427755069eb1c242
Subproject commit c2d9b1ad74375cd315250acbc001106a03b70451