Project

General

Profile

Bug #3679

ESA skin needs to use EML 2.1.0

Added by Shaun Walbridge almost 11 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
registry
Target version:
Start date:
11/19/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3679

Description

Within the registry, the ESA skin has a few special actions to include the moderation data necessary for the ESA workflow. This includes a custom <access> block which needs to be moved to the top level of the document as per EML 2.1.0, and tested.


Related issues

Blocked by Metacat - Bug #3682: ESA skin suffers from security issuesResolved11/19/2008

Blocks Metacat - Bug #3687: Update ESA skin to work with 1.9 paths instead of hard coded valuesResolved11/21/2008

History

#1 Updated by Shaun Walbridge almost 11 years ago

This may take some time: the ESA skin currently uses split() to access the XML, which only works by coincidence and will fail if the document is rearranged in any way. Fixing to use proper XML access methods.

#2 Updated by Shaun Walbridge over 10 years ago

Full circle testing of the ESA registry completed, and remaining bugs fixed in r4758. Fixed issues:
• omit port number from the contextUrl if running on 80, looks bad in exposed URLs
• explicitly pass the metacat object to newAccessionNumber, the global definition of the object had introduced a difficult to track bug
• fix a few variable name esacaping issues
• provide review-related error messages back to the user on the ESA skin (also see related checkin in r4756)
• more EML 2.1 fixes to ESA-specific EML documents

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3679

Also available in: Atom PDF