Differences between revisions 17 and 18
Revision 17 as of 2008-11-10 10:28:55
Size: 3688
Editor: abr
Comment:
Revision 18 as of 2010-03-17 13:09:13
Size: 3688
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 Tasks adressed:: ["TaskA.5"]  Tasks adressed:: [[TaskA.5]]
Line 87: Line 87:
The resource index is detailed in [:Fedora_3.0_triple_store_API:] The resource index is detailed in [[Fedora 3.0 triple store API]]
Line 91: Line 91:
The service has been implemented as a webservice, detailed in ["Risearch_API"]. The code is under review, and has been included in testbed 0.4. The service has been implemented as a webservice, detailed in [[Risearch API]]. The code is under review, and has been included in testbed 0.4.

Action RI Search Wrapper

Assigned
ABR+JRG

Prev assigned

Tasks adressed

TaskA.5

Time estimated
2md

Time used
2.5md

Priority
1

Status
Finished

Iteration
14

Notes

Problem

Mjoelner does not want to speak to the Ressource index themselves. A webservice which encodes the most common requests should be made.

The requests we know of now are:

  • Find the templates in a collection for a given content model
  • Find all objects referencing a list of objects

All these should return lists of PID+title. All should disregard objects in state D (Deleted).

In addition, we need a simple service for checking the state of an object.

The resource index is detailed in Fedora 3.0 triple store API

Progress

The service has been implemented as a webservice, detailed in Risearch API. The code is under review, and has been included in testbed 0.4.

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.

ActionRISearchWrapper (last edited 2010-03-17 13:09:13 by localhost)