## Action = Action Fedora Journaling Evaluation = ## The persons assigned to the action Assigned:: ABR+JRG ## The persons that previously worked on this action Prev assigned:: ## The tasks from the WBS that are adressed by this action Tasks adressed:: [[TaskA.3]] ## The time estimated for this action Time estimated:: 2md ## The time used for this action so far Time used:: 0md ## The priority of this action. 1-9 Priority:: ? ## The status of this action, legal values are 'Not started', 'In progress' and 'Finished' Status:: Finished ## The iteration that this actions belongs to Iteration:: 10 ## Notes about this action, that should be viewable on other pages Notes:: Evalutate on the structural use of Fedora, namely on the use of Journaling Information on Journaling for Fedora: [[http://fedora-commons.org/documentation/2.2.2/userdocs/server/journal/index.html]] Read through this document. Decide on the structural layout of the DOMS system, or more precisely, whether or not journaling should be used. Write a small report detailing the pros and cons of the two choices, and why we chose as we did. ## Detailed description of wanted output from the work to be carried out. ## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written. Needs documentation on what we found out. We did decide that journaling was probably relevant for the usual purposes of journaling, but it was not suitable for using in referential integrity. == Checklist For Working On An Action == 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. * When finishing the action, change the status to "Finished" and update the "time used" field on the action page.