Feature #7576
Add temporal range parsing to dublin core parsing
100%
Description
Lisa Stillwell (DFC) found that DFC content was not returned when searching under the Data Coverage filter in the new DataONE Search UI. Further investigation found that the content of dcterms:temporal element were not parsed correctly when a start/end date combination were part of the literal content string. This ticket defines a new task to add parsing capabilities for the dcterms:temporal element when an xsi:type is "dcterms:Period" and a date range is present in the content field. For example:
start=2016-01; end=2016-01/dcterms:temporal
Relevant link: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#terms-Period
History
#1 Updated by Skye Roseboom almost 9 years ago
- Category set to d1_cn_index_processor
- Assignee changed from Skye Roseboom to Andrei Buium
- Target version set to CCI-2.1.0
- % Done changed from 0 to 30
- Status changed from New to In Progress
#2 Updated by Skye Roseboom almost 9 years ago
- Status changed from In Progress to Testing
- % Done changed from 30 to 50
#3 Updated by Skye Roseboom almost 9 years ago
- Tracker changed from Task to Feature
#4 Updated by Andrei Buium almost 9 years ago
- Tracker changed from Feature to Task
- Status changed from Testing to Closed
- % Done changed from 50 to 100
- translation missing: en.field_remaining_hours set to 0.0
Feature added and tested. (Had to change this from Feature to Task to be able to modify the Status...)
#5 Updated by Andrei Buium almost 9 years ago
- Tracker changed from Task to Feature
