alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2016-04-12

Browse Source 
Signed-off-by: Alan Orth <alan.orth@gmail.com>
This commit is contained in:
Alan Orth
2016-04-12 12:09:18 +03:00
parent dc8805c9b4
commit cee8d20d1b
4 changed files with 57 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -204,6 +204,21 @@ dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and t
<ul>
<li>The donut is already updated and shows the correct number now</li>
<li>CCAFS people say it will only take them an hour to update their code for the metadata renames, so I proposed we&rsquo;d do it tentatively on Monday the 18th.</li>
</ul>
<h2 id="2016-04-12:c88be15f5b2f07c85f7742556a955e47">2016-04-12</h2>
<ul>
<li>Looking at quality of WLE data (<code>cg.subject.iwmi</code>) in SQL:</li>
</ul>
<pre><code>dspacetest=# select text_value, count(*) from metadatavalue where metadata_field_id=217 group by text_value order by count(*) desc;
</code></pre>
<ul>
<li>Listings and Reports is still not returning reliable data for <code>dc.type</code></li>
<li>I think we need to ask Atmire, as their documentation isn&rsquo;t too clear on the format of the filter configs</li>
<li>Alternatively, I want to see if I move all the data from <code>dc.type.output</code> to <code>dc.type</code> and then re-index, if it behaves better</li>
</ul>
</section>

15
public/index.xml
View File

@ -143,6 +143,21 @@ dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and t
&lt;li&gt;The donut is already updated and shows the correct number now&lt;/li&gt;
&lt;li&gt;CCAFS people say it will only take them an hour to update their code for the metadata renames, so I proposed we&amp;rsquo;d do it tentatively on Monday the 18th.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-12:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-12&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Looking at quality of WLE data (&lt;code&gt;cg.subject.iwmi&lt;/code&gt;) in SQL:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;dspacetest=# select text_value, count(*) from metadatavalue where metadata_field_id=217 group by text_value order by count(*) desc;
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Listings and Reports is still not returning reliable data for &lt;code&gt;dc.type&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;I think we need to ask Atmire, as their documentation isn&amp;rsquo;t too clear on the format of the filter configs&lt;/li&gt;
&lt;li&gt;Alternatively, I want to see if I move all the data from &lt;code&gt;dc.type.output&lt;/code&gt; to &lt;code&gt;dc.type&lt;/code&gt; and then re-index, if it behaves better&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

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

@ -143,6 +143,21 @@ dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and t
&lt;li&gt;The donut is already updated and shows the correct number now&lt;/li&gt;
&lt;li&gt;CCAFS people say it will only take them an hour to update their code for the metadata renames, so I proposed we&amp;rsquo;d do it tentatively on Monday the 18th.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-04-12:c88be15f5b2f07c85f7742556a955e47&#34;&gt;2016-04-12&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Looking at quality of WLE data (&lt;code&gt;cg.subject.iwmi&lt;/code&gt;) in SQL:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;dspacetest=# select text_value, count(*) from metadatavalue where metadata_field_id=217 group by text_value order by count(*) desc;
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Listings and Reports is still not returning reliable data for &lt;code&gt;dc.type&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;I think we need to ask Atmire, as their documentation isn&amp;rsquo;t too clear on the format of the filter configs&lt;/li&gt;
&lt;li&gt;Alternatively, I want to see if I move all the data from &lt;code&gt;dc.type.output&lt;/code&gt; to &lt;code&gt;dc.type&lt;/code&gt; and then re-index, if it behaves better&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>