Action Example ContentModels and Templates

Assigned

BAM+JRG

Prev assigned

Tasks adressed

TaskX/1

Time estimated

3md

Time used

1md(BAM) + 1md(JRG) + ?(ABR)

Priority

1

Status

In progress

Iteration

16

Notes

Description

Example objects for several different collections need to be put in the testbed. In order for this to be possible, content models and template objects must first be written. This action comprises the development of the content models and templates. EK will implement the actual example objects - preferably via an installation of the DOMS GUI.

The priorities for subparts of this action

1. Avis (content models already begun, it is said.. before this iteration.)
   • Meeting 2008-12-02 to decide the model for Avis. Time estimate: 1/4 md.

   • merkur.statsbiblioteket.dk/svn/doms/trunk/avis_objects contains 3 content models, 2 schemas and a collection corresponding to data model below.

   • Template objects still missing. Time estimate: 1/4 md.
   • Set up GUI prototype with templates, such that EK can fill in metadata. Time estimate: 1/4 md + EK time.

   • Avis-collection.dia

   • 

2. Radio

   • metadata: PB_Core_radio.doc

   • no model yet. Time estimate: 1md + EK time
3. Valser
   • model is expected to look like spolebaand. Time estimate: 1md + EK time

Progress

Status 2008-12-11

1. Avis: Content models + templates done.

   • merkur.statsbiblioteket.dk/svn/doms/trunk/avis_objects now contains content models, schemas, templates + collection object.

   • The GUI prototype was not set up with templates, such that metadata could be filled in.
2. Radio: Content models + templates done.

   • merkur.statsbiblioteket.dk/svn/doms/trunk/radio_objects contains content models, schemas, templates + collection object.

3. Valser not done!
4. Yearbooks:

   • merkur.statsbiblioteket.dk/svn/doms/trunk/yearbook_collection_V2 contains content models, schemas, templates + test examples.

   • This examples should illustrate reverse relations, but YearbookItem should be changed to also be a main view for GUI.

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.