## Action

= Action Import/Export Examples =



## The persons assigned to the action

 Assigned:: KFC+BAM+TSH



## The persons that previously worked on this action

 Prev assigned::



## The tasks from the WBS that are adressed by this action

 Tasks adressed:: [[TaskE.1]]



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

 Time estimated:: 5md



## The time used for this action so far. Same format as Time estimated

 Time used:: ~1md BAM + ...



## The priority of this action. 1-9

 Priority:: 2



## 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:: 14



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

 Notes:: Export punted





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

We need to give examples of how Import and Export will look in the GUI.

Import and Export are both defined as disseminators on content models.

== Export ==
Code is written for generating an object bundle from a PID and a view. Using this, and an XSLT we should be able to make a reasonable export service. Since we need to investigate Quadriga XML anyway, it would be a good idea to make a first shot at an XSLT generating this from a bundle. The code needs review, the XSLT needs to be written, and it needs to be wrapped in a webservice. A disseminator for this export needs to be added.

'''Export has not been done'''

== Import ==
The code making objects from templates can be used in import. Since integrating with some system to import from is a non-trivial task, this functionality will be mocked up. This means we need to write code that generates some objects that MIGHT have been imported from Horizon, wrap them in a webservice, and add a disseminator for this.

The current (2008-11-10) import mock-up always returns the same object regardless of input bibno. The current disseminator works by way of a jsp page.


== Estimated time ==
 . Review of existing code: 1md
 . Writing XSLT for export: 1md (½md for exploring Quadriga XML, ½md for XSLT)
 . Writing Mockup code for import: 1md
 . Wrapping in webservices (import and export) 1md
 . Creating disseminators (import and export): 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.