Closed adehner closed 7 years ago
I can disable this, but the dcterms:extent is not a dc:extent from OAI-PMH. Is the semantic definition of an extent parsed out of dc:format.
On Fri, Jun 2, 2017 at 1:12 PM, adehner notifications@github.com wrote:
In testing this morning, I see that dcterms:extent is still present when previewing records before contributing a set. We agreed to only harvest mime types from dc:format and I haven't seen dcterms:extent in harvested sets. But it's still appearing when previewing records, which is confusing to Alliance users.
Please remove dcterms:extent from the preview metadata.
Here is a screenshot from my test this morning: [image: screen shot 2017-06-02 at 10 07 01 am] https://cloud.githubusercontent.com/assets/6174191/26736664/ef24d876-477b-11e7-9684-b3dd215c9891.png
@jallibunn https://github.com/jallibunn
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Orbis-Cascade-Alliance/harvester/issues/75, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiX8zti9TskcLS1ZhJeg_9OYusnEgGkks5sAEJ9gaJpZM4NujSL .
Yes, I remember that the dcterms:extent is parsed from dc:format. It's a clever solution for dealing with the digital vs. original format dilemma! But for the time being, the Alliance has decided to keep dc:format harvesting simple, by only harvesting mime types. So please disable dcterms:extent in preview and in harvest.
Okay, I commented out the extent parsing, but it can be re-enabled at some point in the future, if you choose.
In testing this morning, I see that dcterms:extent is still present when previewing records before contributing a set. We agreed to only harvest mime types from dc:format and I haven't seen dcterms:extent in harvested sets. But it's still appearing when previewing records, which is confusing to Alliance users.
Please remove dcterms:extent from the preview metadata.
Here is a screenshot from my test this morning:
@jallibunn