From 9cd6d1ffd13cd95102a0db68c706f1ff8b4b7a0c Mon Sep 17 00:00:00 2001 From: Alan Orth Date: Wed, 20 Apr 2016 19:21:18 +0300 Subject: [PATCH] Add notes for 2016-04-20 --- content/2016-04.md | 25 +++++++++++++++++++++++++ public/2016-04/index.html | 28 ++++++++++++++++++++++++++++ public/index.xml | 28 ++++++++++++++++++++++++++++ public/tags/notes/index.xml | 28 ++++++++++++++++++++++++++++ 4 files changed, 109 insertions(+) diff --git a/content/2016-04.md b/content/2016-04.md index 8a5061c03..444c0844c 100644 --- a/content/2016-04.md +++ b/content/2016-04.md @@ -275,3 +275,28 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error ``` - And then remove them from the metadata registry + +## 2016-04-20 + +- Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server +- Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server +- Field migration went well: + +``` +$ ./migrate-fields.sh +UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66 +UPDATE 40909 +UPDATE metadatavalue SET metadata_field_id=203 WHERE metadata_field_id=76 +UPDATE 51419 +UPDATE metadatavalue SET metadata_field_id=208 WHERE metadata_field_id=82 +UPDATE 5986 +UPDATE metadatavalue SET metadata_field_id=210 WHERE metadata_field_id=88 +UPDATE 2458 +UPDATE metadatavalue SET metadata_field_id=215 WHERE metadata_field_id=106 +UPDATE 3872 +UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108 +UPDATE 46075 +``` + +- Also, I migrated CGSpace to using the PGDG PostgreSQL repo as the infrastructure playbooks had been using it for a while and it seemed to be working well +- Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12) diff --git a/public/2016-04/index.html b/public/2016-04/index.html index ed9dc0267..be3f78378 100644 --- a/public/2016-04/index.html +++ b/public/2016-04/index.html @@ -390,6 +390,34 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error + +

2016-04-20

+ + + +
$ ./migrate-fields.sh
+UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66
+UPDATE 40909
+UPDATE metadatavalue SET metadata_field_id=203 WHERE metadata_field_id=76
+UPDATE 51419
+UPDATE metadatavalue SET metadata_field_id=208 WHERE metadata_field_id=82
+UPDATE 5986
+UPDATE metadatavalue SET metadata_field_id=210 WHERE metadata_field_id=88
+UPDATE 2458
+UPDATE metadatavalue SET metadata_field_id=215 WHERE metadata_field_id=106
+UPDATE 3872
+UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108
+UPDATE 46075
+
+ + diff --git a/public/index.xml b/public/index.xml index 703da6226..f9a76d45f 100644 --- a/public/index.xml +++ b/public/index.xml @@ -329,6 +329,34 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error <ul> <li>And then remove them from the metadata registry</li> </ul> + +<h2 id="2016-04-20:c88be15f5b2f07c85f7742556a955e47">2016-04-20</h2> + +<ul> +<li>Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server</li> +<li>Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server</li> +<li>Field migration went well:</li> +</ul> + +<pre><code>$ ./migrate-fields.sh +UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66 +UPDATE 40909 +UPDATE metadatavalue SET metadata_field_id=203 WHERE metadata_field_id=76 +UPDATE 51419 +UPDATE metadatavalue SET metadata_field_id=208 WHERE metadata_field_id=82 +UPDATE 5986 +UPDATE metadatavalue SET metadata_field_id=210 WHERE metadata_field_id=88 +UPDATE 2458 +UPDATE metadatavalue SET metadata_field_id=215 WHERE metadata_field_id=106 +UPDATE 3872 +UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108 +UPDATE 46075 +</code></pre> + +<ul> +<li>Also, I migrated CGSpace to using the PGDG PostgreSQL repo as the infrastructure playbooks had been using it for a while and it seemed to be working well</li> +<li>Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)</li> +</ul> diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml index dd7fc9045..968ce75d2 100644 --- a/public/tags/notes/index.xml +++ b/public/tags/notes/index.xml @@ -329,6 +329,34 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error <ul> <li>And then remove them from the metadata registry</li> </ul> + +<h2 id="2016-04-20:c88be15f5b2f07c85f7742556a955e47">2016-04-20</h2> + +<ul> +<li>Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server</li> +<li>Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server</li> +<li>Field migration went well:</li> +</ul> + +<pre><code>$ ./migrate-fields.sh +UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66 +UPDATE 40909 +UPDATE metadatavalue SET metadata_field_id=203 WHERE metadata_field_id=76 +UPDATE 51419 +UPDATE metadatavalue SET metadata_field_id=208 WHERE metadata_field_id=82 +UPDATE 5986 +UPDATE metadatavalue SET metadata_field_id=210 WHERE metadata_field_id=88 +UPDATE 2458 +UPDATE metadatavalue SET metadata_field_id=215 WHERE metadata_field_id=106 +UPDATE 3872 +UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108 +UPDATE 46075 +</code></pre> + +<ul> +<li>Also, I migrated CGSpace to using the PGDG PostgreSQL repo as the infrastructure playbooks had been using it for a while and it seemed to be working well</li> +<li>Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)</li> +</ul>