Ticket #569 (closed requirement: fixed)
Harvested GEMINI document metadata validation
Reported by: | johnbywater | Owned by: | thejimmyg |
---|---|---|---|
Priority: | major | Milestone: | ckan-v1.4 |
Component: | uklii | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description
Change History
comment:7 Changed 4 years ago by johnbywater
- sprint changed from 1.2.5 to 1.2.6
Moved from sprint 1.2.5
comment:8 Changed 4 years ago by johnbywater
- sprint changed from 1.2.6 to 1.2.8
Moved from sprint 1.2.6
comment:10 Changed 4 years ago by johnbywater
- sprint changed from 1.2.8 to 1.2.9
Moved from sprint 1.2.8
comment:12 Changed 4 years ago by johnbywater
- sprint changed from 1.3.0 to 1.3.1
Moved from sprint 1.3.0
comment:13 Changed 3 years ago by thejimmyg
- Owner changed from johnbywater to thejimmyg
- Priority set to major
- Type changed from story to requirement
- Component set to uklii
- Summary changed from Validate metadata document against XML schema to Harvested GEMINI document metadata validation
Our metadata validation will consist of:
- Testing the schema
- Testing the schematron
- Checking we can get out the data we need
comment:14 Changed 3 years ago by wwaites
so this means a dependency on amara (finally). on the plus side it is one of the better xml python libraries, xpath, xslt, etc. on the down side it how many xml libraries do we depend on and use now? this is for the schematron...
comment:15 Changed 3 years ago by wwaites
*sigh* but it relies on 4suite in version 1.x and amara2 doesn't have the schematron anymore...
comment:16 Changed 3 years ago by wwaites
*sigh* again. the gemini schematron schema isn't compatible with the amara scimitar... despite the instructions to use the implementation from schematron.com...
comment:17 Changed 3 years ago by thejimmyg
- Status changed from new to closed
- Resolution set to fixed
This is now complete in ckanext-csw.