mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-26 00:18:21 +01:00
Add notes for 2016-06-09
This commit is contained in:
parent
7d7e9775df
commit
06dfd8da30
@ -147,3 +147,9 @@ $ xml sel -t -m '//value-pairs[@value-pairs-name="ilrisubject"]/pair/displayed-v
|
|||||||
- Seems to be a virtual field that is queried from the authority cache... hmm
|
- Seems to be a virtual field that is queried from the authority cache... hmm
|
||||||
- In other news, I found out that the About page that we haven't been using lives in `dspace/config/about.xml`, so now we can update the text
|
- In other news, I found out that the About page that we haven't been using lives in `dspace/config/about.xml`, so now we can update the text
|
||||||
- File bug about `closed="true"` attribute of controlled vocabularies not working: https://jira.duraspace.org/browse/DS-3238
|
- File bug about `closed="true"` attribute of controlled vocabularies not working: https://jira.duraspace.org/browse/DS-3238
|
||||||
|
|
||||||
|
## 2016-06-09
|
||||||
|
|
||||||
|
- Atmire explained that the `atmire.orcid.id` field doesn't exist in the schema, as it actually comes from the authority cache during XMLUI run time
|
||||||
|
- This means we don't see it when harvesting via OAI or REST, for example
|
||||||
|
- They opened a feature ticket on the DSpace tracker to ask for support of this: https://jira.duraspace.org/browse/DS-3239
|
||||||
|
@ -244,6 +244,14 @@ UPDATE 960
|
|||||||
<li>Seems to be a virtual field that is queried from the authority cache… hmm</li>
|
<li>Seems to be a virtual field that is queried from the authority cache… hmm</li>
|
||||||
<li>In other news, I found out that the About page that we haven’t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
<li>In other news, I found out that the About page that we haven’t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
||||||
<li>File bug about <code>closed="true"</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
<li>File bug about <code>closed="true"</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<h2 id="2016-06-09:6783872e82b68b1517e00f494e6b6504">2016-06-09</h2>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>Atmire explained that the <code>atmire.orcid.id</code> field doesn’t exist in the schema, as it actually comes from the authority cache during XMLUI run time</li>
|
||||||
|
<li>This means we don’t see it when harvesting via OAI or REST, for example</li>
|
||||||
|
<li>They opened a feature ticket on the DSpace tracker to ask for support of this: <a href="https://jira.duraspace.org/browse/DS-3239">https://jira.duraspace.org/browse/DS-3239</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
</section>
|
</section>
|
||||||
|
@ -183,6 +183,14 @@ UPDATE 960
|
|||||||
<li>In other news, I found out that the About page that we haven&rsquo;t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
<li>In other news, I found out that the About page that we haven&rsquo;t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
||||||
<li>File bug about <code>closed=&quot;true&quot;</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
<li>File bug about <code>closed=&quot;true&quot;</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
<h2 id="2016-06-09:6783872e82b68b1517e00f494e6b6504">2016-06-09</h2>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>Atmire explained that the <code>atmire.orcid.id</code> field doesn&rsquo;t exist in the schema, as it actually comes from the authority cache during XMLUI run time</li>
|
||||||
|
<li>This means we don&rsquo;t see it when harvesting via OAI or REST, for example</li>
|
||||||
|
<li>They opened a feature ticket on the DSpace tracker to ask for support of this: <a href="https://jira.duraspace.org/browse/DS-3239">https://jira.duraspace.org/browse/DS-3239</a></li>
|
||||||
|
</ul>
|
||||||
</description>
|
</description>
|
||||||
</item>
|
</item>
|
||||||
|
|
||||||
|
@ -183,6 +183,14 @@ UPDATE 960
|
|||||||
<li>In other news, I found out that the About page that we haven&rsquo;t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
<li>In other news, I found out that the About page that we haven&rsquo;t been using lives in <code>dspace/config/about.xml</code>, so now we can update the text</li>
|
||||||
<li>File bug about <code>closed=&quot;true&quot;</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
<li>File bug about <code>closed=&quot;true&quot;</code> attribute of controlled vocabularies not working: <a href="https://jira.duraspace.org/browse/DS-3238">https://jira.duraspace.org/browse/DS-3238</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
<h2 id="2016-06-09:6783872e82b68b1517e00f494e6b6504">2016-06-09</h2>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>Atmire explained that the <code>atmire.orcid.id</code> field doesn&rsquo;t exist in the schema, as it actually comes from the authority cache during XMLUI run time</li>
|
||||||
|
<li>This means we don&rsquo;t see it when harvesting via OAI or REST, for example</li>
|
||||||
|
<li>They opened a feature ticket on the DSpace tracker to ask for support of this: <a href="https://jira.duraspace.org/browse/DS-3239">https://jira.duraspace.org/browse/DS-3239</a></li>
|
||||||
|
</ul>
|
||||||
</description>
|
</description>
|
||||||
</item>
|
</item>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user