Project

General

Profile

Bug #3035

Generated resource maps contain invalid representation of xsd:date

Added by Dave Vieglais about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
Metacat
Start date:
2012-06-29
Due date:
% Done:

100%

Milestone:
CCI-1.0.4
Product Version:
*
Story Points:
Sprint:

Description

For example, the resource map:

https://knb.ecoinformatics.org/knb/d1/mn/v1/object/resourceMap_kgordon.4.24

contains an entry:

2012-06-22T22:19:31-0700/dcterms:modified

There are two problems with this:

  1. The type should be dateTime
  2. The timezone offset should include a colon, i.e. "-07:00" instead of "-0700"

Issue 1 can be corrected in the foresite library:

http://code.google.com/p/foresite-toolkit/source/browse/foresite-java/trunk/src/main/java/org/dspace/foresite/jena/JenaOREConstants.java


Subtasks

Task #3040: url encode URIs used in ORE mapsClosedBen Leinfelder


Related issues

Related to Infrastructure - Task #3046: Create utility to update ORE maps with invalid date formats In Progress 2012-07-02

History

#1 Updated by Ben Leinfelder about 8 years ago

  • Status changed from New to In Progress

Reworking the foresite library. I took out the use of SimpleDateFormat because that doesn't provide the correct serialization of timezone for the xsd:dateTime type.
The resulting rdf fragment is now:
2012-06-29T09:27:48.991-07:00/dcterms:modified
Note that partial seconds are now included which I believe is still valid for xsd:dateTime since it came directly from javax.xml.bind.DatatypeConverter.printDateTime().

Will need to include this in the foresite project and make the change available as an official (non-SNAPSHOT) release.

#2 Updated by Ben Leinfelder about 8 years ago

#3 Updated by Ben Leinfelder about 8 years ago

Another thing that I wanted to ask is whether we need explicit URL escaping of the slashes and colons in the resolve URIs:

#4 Updated by Dave Vieglais about 8 years ago

Ben Leinfelder wrote:

Another thing that I wanted to ask is whether we need explicit URL escaping of the slashes and colons in the resolve URIs:

Yes.

#5 Updated by Dave Vieglais about 8 years ago

  • Position set to 5

#6 Updated by Ben Leinfelder about 8 years ago

  • Position set to 1
  • Position deleted (8)
  • Target version changed from Sprint-2012.27-Block.4.2 to Sprint-2012.29-Block.4.3

#7 Updated by Dave Vieglais about 8 years ago

  • Milestone changed from CCI-1.0.3 to CCI-1.0.4

#8 Updated by Ben Leinfelder almost 8 years ago

  • Status changed from In Progress to Closed

the underlying cause has been addressed, just need to fix existing ORE maps in the wild (as documented in related task)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)