|
Size: 2995
Comment:
|
← Revision 13 as of 2010-03-17 13:09:19 ⇥
Size: 3389
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from ActionCreateObjectFromTemplate | |
| Line 14: | Line 15: |
| Line 21: | Line 21: |
| Tasks adressed:: ["TaskX/1"] | Tasks adressed:: [[TaskE.1]] |
| Line 27: | Line 27: |
| Time estimated:: not done | Time estimated:: 2md |
| Line 33: | Line 33: |
| Time used:: 0md | Time used:: 3.5 md |
| Line 39: | Line 39: |
| Priority:: ? | Priority:: 1 |
| Line 45: | Line 45: |
| Status:: Not described |
Status:: Finished |
| Line 51: | Line 50: |
| Iteration:: 0 | Iteration:: 14 |
| Line 67: | Line 66: |
| We have promised Mjølner a webservice, that given the PID of a template, returns the PID a new object which is cloned from the old object and ingested into Fedora. | |
| Line 68: | Line 68: |
| Code has been written to copy a template, replace the PID, and ingest the object. This needs to be reviewed and wrapped in a webservice. | |
| Line 69: | Line 70: |
| Estimated time: Review: 1md Wrap in webservice: 1md |
Action Create Objects from Template
- Assigned
- TSH+JRG+KFC
- Prev assigned
- Tasks adressed
- Time estimated
- 2md
- Time used
- 3.5 md
- Priority
- 1
- Status
- Finished
- Iteration
- 14
- Notes
We have promised Mjølner a webservice, that given the PID of a template, returns the PID a new object which is cloned from the old object and ingested into Fedora.
Code has been written to copy a template, replace the PID, and ingest the object. This needs to be reviewed and wrapped in a webservice.
Estimated time: Review: 1md Wrap in webservice: 1md
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.