|
Size: 2969
Comment:
|
← Revision 5 as of 2010-03-17 13:09:22 ⇥
Size: 3924
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
= Action TITLE = |
= Action Validator = |
| Line 8: | Line 4: |
| Line 10: | Line 5: |
| Line 14: | Line 6: |
| Line 16: | Line 7: |
| Line 20: | Line 8: |
Tasks adressed:: ["TaskX/1"] |
Tasks adressed:: [[TaskA.4]], [[TaskC.3]] |
| Line 26: | Line 10: |
| Line 28: | Line 11: |
| Line 32: | Line 12: |
| Line 34: | Line 13: |
| Line 38: | Line 14: |
| Line 40: | Line 15: |
| Line 44: | Line 16: |
Status:: Not described |
Status:: Description in progress |
| Line 50: | Line 18: |
| Line 52: | Line 19: |
| Line 56: | Line 20: |
Notes:: |
Notes:: |
| Line 64: | Line 22: |
| Line 67: | Line 24: |
| == Problem == We need to write a webservice, that given a pid, applies the an XML schema validator to each datastream with a schema, and an OWL Lite validator for an OWL document containing the Content Model ontology and the RELS-EXT datastream from the object (with the fedora-model:hasModel property replaced with rdf:type). |
|
| Line 68: | Line 27: |
| Code exists, that given an object finds the correct Schema for each datastream, and generates the correct Ontology from the Content Model of an object. This code needs to be reviewed. | |
| Line 69: | Line 29: |
| TODO: Should we validate CONTENT datastreams? | |
| Line 70: | Line 31: |
| We need to hook fedora-APIM methods to do the following: * Fail on any modifying call on active objects, except if the call invalidates them * Apply validation code when an object is set to valid * Apply validation code on ingest, unless ingested object is inactive [TODO: Should we simply inactivate the ingested object(by modifying the XML) for ease of code, and simply reactivate it?] |
|
| Line 71: | Line 36: |
| We probably need to massage the output of the validators, as well. | |
| Line 72: | Line 38: |
| == Notes == | |
| Line 78: | Line 42: |
| The Life Cycle of an Action: | |
| Line 79: | Line 44: |
The Life Cycle of an Action: |
|
| Line 89: | Line 51: |
| Line 92: | Line 53: |
| Line 95: | Line 54: |
| Line 97: | Line 55: |
| Line 99: | Line 56: |
Action Validator
- Assigned
- KFC+ABR
- Prev assigned
- Time estimated
- not done
- Time used
- 0md
- Priority
- 2
- Status
- Description in progress
- Iteration
- 14
- Notes
Problem
We need to write a webservice, that given a pid, applies the an XML schema validator to each datastream with a schema, and an OWL Lite validator for an OWL document containing the Content Model ontology and the RELS-EXT datastream from the object (with the fedora-model:hasModel property replaced with rdf:type).
Code exists, that given an object finds the correct Schema for each datastream, and generates the correct Ontology from the Content Model of an object. This code needs to be reviewed.
TODO: Should we validate CONTENT datastreams?
We need to hook fedora-APIM methods to do the following:
- Fail on any modifying call on active objects, except if the call invalidates them
- Apply validation code when an object is set to valid
- Apply validation code on ingest, unless ingested object is inactive [TODO: Should we simply inactivate the ingested object(by modifying the XML) for ease of code, and simply reactivate it?]
We probably need to massage the output of the validators, as well.
Notes
Checklist For Working On An Action
The Life Cycle of an Action:
Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned
Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.
Review the definition: Get another project group member to review the action definition, and update it.
Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.
Implement the action: See details below
Review the action: Get another project group member to review what is implemented (code and documentation), and update it.
Finish the action: Change the status to "Finished" and update the "time used" field on the action page.
Please make sure that you address the below issues, when working on an action:
- Update the state of the action to "In Progress" when you start working on it.
- Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.
- Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.