alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-12-23 21:44:30 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2016-04-20

Browse Source
This commit is contained in:
Alan Orth 2016-04-20 19:21:18 +03:00
parent 5ec064879c
commit 9cd6d1ffd1
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
4 changed files with 109 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
content/2016-04.md
View File

@ -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)

28
public/2016-04/index.html
View File

@ -390,6 +390,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>
</section>

28
public/index.xml
View File

@ -329,6 +329,34 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error
&lt;ul&gt;
&lt;li&gt;And then remove them from the metadata registry&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-20:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-20&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server&lt;/li&gt;
&lt;li&gt;Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server&lt;/li&gt;
&lt;li&gt;Field migration went well:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;$ ./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
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;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&lt;/li&gt;
&lt;li&gt;Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

28
public/tags/notes/index.xml
View File

@ -329,6 +329,34 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error
&lt;ul&gt;
&lt;li&gt;And then remove them from the metadata registry&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-20:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-20&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server&lt;/li&gt;
&lt;li&gt;Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server&lt;/li&gt;
&lt;li&gt;Field migration went well:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;$ ./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
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;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&lt;/li&gt;
&lt;li&gt;Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>