## Action

= Action PW Remove =



## The persons assigned to the action

 Assigned:: BAM


## The persons that previously worked on this action

 Prev assigned::



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

 Tasks adressed:: [[TaskX/1]]



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

 Time estimated:: 2md



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

 Time used:: 0md



## The priority of this action. 1-9

 Priority:: 4



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

 Status:: Description not reviewed



## The iteration that this actions belongs to

 Iteration:: 15



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

 Notes:: also localhost:8080



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

Currently (2008-11-27) username and password to Fedora and also {{{localhost:8080}}} is hardcoded a number of places. The username and password should always be given as parameters to the webservices, and fedoraServerHost and fedoraServerPort can be given in a configuration or properties file?

 * We will investigate the number of affected places, and make sure that we do not need to change any interfaces. Time estimate: ½md.
 * We will remove the hardcoded username and password. Time estimate: ½md.
 * We will introduce a properties file - or can we use {{{fedora/server/config/fedora.fcfg}}}? Time estimate: 1md.

== Investigation Hardcoded Username + PW ==
 * RIquery_webservice: only in test, ok
 * disseminator_webservice: no longer used, ok
 * domsutils introduces a DomsUserToken, which has a hardcoded username + pw default...
 * import_from_horizon_webservice: only in test, ok
 * ingest: no longer used, ok
 * minidoms: no longer used, ok
 * objectcreation_webservice: only in test, ok
 * search_webservice: class SearchWS uses hardcoded username + pw to prepare connection, soon to be outdated?
 * SummaFace: uses hardcoded username + pw to create DomsUserToken... 
 * testbed: install.sh + INSTALL uses hardcoded username + pw

To summarise, assuming search webservice is outdated, we only have hardcoded username + pw in connection with DomsUserToken (domsutils + SummaFace) and in testbed.

== Investigation Hardcoded Host + Port ==
TODO

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