Action Metadata Standards

Assigned

KFC+JRG+EK

Prev assigned

Tasks adressed

TaskA.2

Time estimated

5½md + Elsebeths time

Time used

1.5h

Priority

1

Status

Not started

Iteration

13

Notes

We need to have decisions on metadata standards used in base collection and the test collection. Currently we have the following under discussion:

• Dublin Core
• Qualified Dublin Core
• Premis; events

We need to make sure we have the same understanding about what this means, and how it is described in XML.

Also, we need to make sure that these are indeed reasonable choices for metadata standards.

This will mean having a meeting with Elsebeth, where we make absolutely sure we have the same understandings about

• What does e.g. Qualified Dublin Core mean
• Which fields do we expect to fill out, and how
• What exactly are "qualifiers", how do they look in the XML metadata and how could we see that in the UI?
• Is premis in any way usable? How will it look?

We also need to talk to Mjølner about what kinds of XML Schema are reasonable and required to generate a UI - and can we avoid restricting this too much?

Time estimate is as follows:

• Meeting with Elsebeth: ½ md per participant, three times
• Elsebeth time on working with datamodels: Unknown?
• Meeting with Mjølner about XML schema: ½ md per participant
• Updating Data model documentation with results: ½md
• Updating base collection and test objects with results: 1 md

Assuming 2 DOMS participants per meeting, this gives 5½md + Elsebeths time

Description reviewed -- bam 2008-09-23 12:49:24.

Progress

First meeting about metadata standards

Present: ABR, JRG, EK. 30min each We discussed the doms object model, and how metadata attach to it. A common understanding about how this is done in doms was reached.

Further work:

• JRG will send the Reel tape data model illustration and the sample xsd code to EK. DONE
• EK will report back descriptions of the QDC schemas to be used in this model.
• DOMS developers will confer further with her, when this happens

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.