mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Update theme and regenerate public
This commit is contained in:
@ -2,38 +2,51 @@
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
|
||||
|
||||
|
||||
|
||||
<meta charset="utf-8">
|
||||
<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 name="description" content="">
|
||||
<meta name="author" content="Alan Orth">
|
||||
<meta property="og:title" content="November, 2016" />
|
||||
<meta property="og:description" content="2016-11-01 Add dc.type to the output options for Atmire’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." />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2016-11/" />
|
||||
|
||||
|
||||
<meta property="og:updated_time" content="2016-11-01T09:21:00+03:00"/>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- OpenGraph Metadata: http://ogp.me/ -->
|
||||
<meta property="og:title" content="November, 2016">
|
||||
<meta property="og:description" content="">
|
||||
|
||||
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="article:published_time" content="2016-11-01T09:21:00+03:00">
|
||||
<meta property="article:author" content="Alan Orth">
|
||||
|
||||
<meta itemprop="name" content="November, 2016">
|
||||
<meta itemprop="description" content="2016-11-01 Add dc.type to the output options for Atmire’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.">
|
||||
|
||||
|
||||
<meta itemprop="dateModified" content="2016-11-01T09:21:00+03:00" />
|
||||
<meta itemprop="wordCount" content="1152">
|
||||
|
||||
|
||||
|
||||
<meta itemprop="keywords" content="notes," />
|
||||
|
||||
|
||||
|
||||
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2016-11/">
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
|
||||
|
||||
|
||||
<meta name="twitter:title" content="November, 2016"/>
|
||||
<meta name="twitter:description" content="2016-11-01 Add dc.type to the output options for Atmire’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."/>
|
||||
|
||||
|
||||
|
||||
<!-- Metadata for Twitter: https://dev.twitter.com/cards/markup -->
|
||||
|
||||
<meta property="twitter:card" content="summary">
|
||||
|
||||
|
||||
<meta property="twitter:title" content="November, 2016">
|
||||
<meta property="twitter:description" content="">
|
||||
|
||||
|
||||
|
||||
@ -52,8 +65,11 @@
|
||||
<!-- combined, minified CSS -->
|
||||
<link href="https://alanorth.github.io/cgspace-notes/css/style.css" rel="stylesheet">
|
||||
|
||||
<!-- RSS 2.0 feed -->
|
||||
<link href="https://alanorth.github.io/cgspace-notes/index.xml" type="application/rss+xml" rel="alternate">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
@ -79,6 +95,8 @@
|
||||
<div class="col-sm-8 blog-main">
|
||||
|
||||
|
||||
|
||||
|
||||
<article class="blog-post">
|
||||
<header>
|
||||
<h2 class="blog-post-title"><a href="https://alanorth.github.io/cgspace-notes/2016-11/">November, 2016</a></h2>
|
||||
@ -286,7 +304,7 @@ dspace=# select count(text_value) from metadatavalue where resource_type_id=2 an
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Generate a list of all these so I can fix them in batch:</li>
|
||||
<li>Generate a list of all these so I can maybe fix them in batch:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>dspace=# \copy (select distinct text_lang, count(*) from metadatavalue where resource_type_id=2 group by text_lang order by count desc) to /tmp/text-langs.csv with csv;
|
||||
@ -301,16 +319,50 @@ COPY 14
|
||||
UPDATE 85
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>The <code>fix-metadata.py</code> script I have is meant for specific metadata values, so if I want to update some <code>text_lang</code> values I should just do it directly in the database</li>
|
||||
<li>For example, on a limited set:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>dspace=# update metadatavalue set text_lang=NULL where resource_type_id=2 and metadata_field_id=203 and text_value='LIVESTOCK' and text_lang='';
|
||||
UPDATE 420
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>And assuming I want to do it for all fields:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>dspacetest=# update metadatavalue set text_lang=NULL where resource_type_id=2 and text_lang='';
|
||||
UPDATE 183726
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>After that restarted Tomcat and PostgreSQL (because I’m superstitious about caches) and now I see the following in REST API query:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X POST "http://localhost:8080/rest/items/find-by-metadata-field" -d '{"key": "cg.subject.ilri","value": "SEEDS"}' | jq length
|
||||
71
|
||||
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X POST "http://localhost:8080/rest/items/find-by-metadata-field" -d '{"key": "cg.subject.ilri","value": "SEEDS", "language":""}' | jq length
|
||||
0
|
||||
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X POST "http://localhost:8080/rest/items/find-by-metadata-field" -d '{"key": "cg.subject.ilri","value": "SEEDS", "language":"en_US"}' | jq length
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Not sure what’s going on, but Discovery shows 83 values, and database shows 85, so I’m going to reindex Discovery just in case</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</div> <!-- /.blog-main -->
|
||||
|
||||
|
||||
<aside class="col-sm-3 offset-sm-1 blog-sidebar">
|
||||
<aside class="col-sm-3 offset-sm-1 blog-sidebar">
|
||||
|
||||
|
||||
|
||||
@ -348,7 +400,6 @@ UPDATE 85
|
||||
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
</div> <!-- /.row -->
|
||||
</div> <!-- /.container -->
|
||||
|
||||
Reference in New Issue
Block a user