## Please put instances of this page in the Actions/ subfolder
= Action Hook ECM API =
## The persons assigned to the action
 Assigned:: ABR(2md), JRG(1md)

## The persons that previously worked on this action
 Prev assigned::

## The tasks from the WBS that are adressed by this action
 Tasks adressed:: [[Tasks/3/2]]

## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated
 Time estimated:: 3md

## The time used for this action so far. Same format as Time estimated
 Time used:: 1.5md(ABR), 0.5md(JRG)

## The priority of this action. 1-9. 1 is highest.
 Priority:: 5

## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished'
 Status:: Finished

## The iteration that this actions belongs to
 Iteration:: 21

## Notes about this action, that should be viewable on other pages
 Notes:: 


== Problem ==
Fedora has a object property called state. We want to use this state. To do so, we have made the following rules

 1. No objects in the Active state can be altered
 1. No object can be put in the Active state without being validated

The first rule should be enforced as a repository wide XACML policy. 
The second should be done as a hook into the Api function ModifyObject


== Progress ==

The api hook have been completed. It is a jar file, that must be installed on the Fedora classpath. It is set up as a Management decorator in fedora.fcfg. It has been sporadically tested, and works.

The xacml policy have been achieved
== Result ==

The result of this action can be found in the module FedoraApiHooks in the Ecm project


== 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.