|
Size: 4247
Comment:
|
Size: 4250
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| Tasks adressed:: ["Tasks/1/1/1"], ["Tasks/1/1/2"], ["Tasks/1/2"], ["Tasks/1/3"], ["Tasks/1/4"], ["Tasks/1/5"], ["Tasks/7/2"], | Tasks adressed:: [[Tasks/1/1/1]], [[Tasks/1/1/2]], [[Tasks/1/2]], [[Tasks/1/3]], [[Tasks/1/4]], [[Tasks/1/5]], [[Tasks/7/2]], |
| Line 38: | Line 38: |
| * We describe FRBR and give examples of how the model may be used in general. See ["How to use FRBR"] | * We describe FRBR and give examples of how the model may be used in general. See [[How to use FRBR]] |
| Line 40: | Line 40: |
| * We examine how we can modify the FRBR-datamodel to fit into Fedora - and how we can combine it with the Patterne Language-model. See Diagram shown (with comments) on [:DataModelWorkDiagram]. Also see [:GuidelinesForNewDatamodel/PatternLanguage/FRBR_Relations] | * We examine how we can modify the FRBR-datamodel to fit into Fedora - and how we can combine it with the Patterne Language-model. See Diagram shown (with comments) on [[DataModelWorkDiagram]]. Also see [[GuidelinesForNewDatamodel/PatternLanguage/FRBR Relations]] |
| Line 42: | Line 42: |
| * We analyse the digitisation workflow in view of the datamodel and the GUI. See ["Analyse Workflow"] | * We analyse the digitisation workflow in view of the datamodel and the GUI. See [[Analyse Workflow]] |
| Line 44: | Line 44: |
| * We design the datamodel and comply with [:GuidelinesForNewDatamodel]. | * We design the datamodel and comply with [[GuidelinesForNewDatamodel]]. |
| Line 46: | Line 46: |
| * We decide on the relevant entities of the PREMIS semantic units. See ["PREMIS in DOMS"] | * We decide on the relevant entities of the PREMIS semantic units. See [[PREMIS in DOMS]] |
Action Datamodel
- Assigned
- EAB: ? PKO: 1 EK: ?
- Prev assigned
- Tasks adressed
Tasks/1/1/1, Tasks/1/1/2, Tasks/1/2, Tasks/1/3, Tasks/1/4, Tasks/1/5, Tasks/7/2,
- Time remaining
- 2md
- Time estimated
- 11md
- Priority
- 8
- Status
- In progress
- Iteration
- 23,24
- Notes
In this action, we intend to describe the DOMS datamodel. This includes an evaluation of the use of FRBR for DOMS.
The outcome of the seven tasks will (hopefully) be a basic datamodel for all present and future digital collections in DOMS.
We describe FRBR and give examples of how the model may be used in general. See How to use FRBR
We examine how we can modify the FRBR-datamodel to fit into Fedora - and how we can combine it with the Patterne Language-model. See Diagram shown (with comments) on DataModelWorkDiagram. Also see GuidelinesForNewDatamodel/PatternLanguage/FRBR Relations
We analyse the digitisation workflow in view of the datamodel and the GUI. See Analyse Workflow
We design the datamodel and comply with GuidelinesForNewDatamodel.
We decide on the relevant entities of the PREMIS semantic units. See PREMIS in DOMS
- We will test the datamodel in relation to Fedora and GUI.
- The relevant documentation will be extracted and published
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.