diff --git a/content/2016-03.md b/content/2016-03.md index fa579bfb2..c84fdf2ea 100644 --- a/content/2016-03.md +++ b/content/2016-03.md @@ -187,3 +187,10 @@ Can't find method org.dspace.app.xmlui.aspect.administrative.FlowGroupUtils.proc - Looks like the Listings and Reports fix was NOT due to the search indexes (which are actually not used), and rather due to the filter configuration in the Listings and Reports config - This pull request simply updates the config for the dc.type.output → dc.type change that was made last week: https://github.com/ilri/DSpace/pull/204 - Deploy robots.txt fix, embargo for item submissions, and listings and reports fix on CGSpace + +## 2016-03-29 + +- Skype meeting with Peter and Addis team to discuss metadata changes for Dublin Core, CGcore, and CGSpace-specific fields +- We decided to proceed with some deletes first, then identify CGSpace-specific fields to clean/move to `cg.*`, and then worry about broader changes to DC +- Before we move or rename and fields we need to circulate a list of fields we intend to change to CCAFS, CWPF, etc who might be harvesting the fields +- After all of this we need to start implementing controlled vocabularies for fields, either with the Javascript lookup or like existing ILRI subjects diff --git a/public/2016-03/index.html b/public/2016-03/index.html index 832e89c17..7a4897658 100644 --- a/public/2016-03/index.html +++ b/public/2016-03/index.html @@ -306,6 +306,15 @@
  • Looks like the Listings and Reports fix was NOT due to the search indexes (which are actually not used), and rather due to the filter configuration in the Listings and Reports config
  • This pull request simply updates the config for the dc.type.output → dc.type change that was made last week: https://github.com/ilri/DSpace/pull/204
  • Deploy robots.txt fix, embargo for item submissions, and listings and reports fix on CGSpace
  • + + +

    2016-03-29

    + + diff --git a/public/index.xml b/public/index.xml index 83714e9a3..8d6df96f9 100644 --- a/public/index.xml +++ b/public/index.xml @@ -245,6 +245,15 @@ <li>This pull request simply updates the config for the dc.type.output → dc.type change that was made last week: <a href="https://github.com/ilri/DSpace/pull/204">https://github.com/ilri/DSpace/pull/204</a></li> <li>Deploy robots.txt fix, embargo for item submissions, and listings and reports fix on CGSpace</li> </ul> + +<h2 id="2016-03-29:5a28ddf3ee658c043c064ccddb151717">2016-03-29</h2> + +<ul> +<li>Skype meeting with Peter and Addis team to discuss metadata changes for Dublin Core, CGcore, and CGSpace-specific fields</li> +<li>We decided to proceed with some deletes first, then identify CGSpace-specific fields to clean/move to <code>cg.*</code>, and then worry about broader changes to DC</li> +<li>Before we move or rename and fields we need to circulate a list of fields we intend to change to CCAFS, CWPF, etc who might be harvesting the fields</li> +<li>After all of this we need to start implementing controlled vocabularies for fields, either with the Javascript lookup or like existing ILRI subjects</li> +</ul> diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml index 2aa047f2c..bbba85d4e 100644 --- a/public/tags/notes/index.xml +++ b/public/tags/notes/index.xml @@ -245,6 +245,15 @@ <li>This pull request simply updates the config for the dc.type.output → dc.type change that was made last week: <a href="https://github.com/ilri/DSpace/pull/204">https://github.com/ilri/DSpace/pull/204</a></li> <li>Deploy robots.txt fix, embargo for item submissions, and listings and reports fix on CGSpace</li> </ul> + +<h2 id="2016-03-29:5a28ddf3ee658c043c064ccddb151717">2016-03-29</h2> + +<ul> +<li>Skype meeting with Peter and Addis team to discuss metadata changes for Dublin Core, CGcore, and CGSpace-specific fields</li> +<li>We decided to proceed with some deletes first, then identify CGSpace-specific fields to clean/move to <code>cg.*</code>, and then worry about broader changes to DC</li> +<li>Before we move or rename and fields we need to circulate a list of fields we intend to change to CCAFS, CWPF, etc who might be harvesting the fields</li> +<li>After all of this we need to start implementing controlled vocabularies for fields, either with the Javascript lookup or like existing ILRI subjects</li> +</ul>