AVH Work Plans

This page documents current application development, systems and infrastructure work plans for the AVH. Edit this page to indicate current and projected work and estimated resources involved or to be sought.

= AVH server side applications =

Application development on the server or provider side of the AVH application

= AVH client side applications =

Application development on the client side or user interface side of the AVH application

= Herbaria applications =

The following sections cover work plans for AVH development activity within individual AVH participants.

ABRS

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

AD

 * Project title. Implement BioCASE in production.


 * Description. Currently the Adelaide BioCASE provider and associated MySQL database are running on the Department's QA computer. As is the Oracle mirror of the source Texpress specimen database. These all need to be implemented on the Department's matching production computer.


 * Background. Development of Adelaide's BioCASE provide system for AVH occurred on our QA computer. AVH only queries AD once a night for updates. If the QA computer is down for an extended period, there is little consequence since AVH will eventually query all the outstanding new records. However, the system should be running on our production computer, which has greater uptime guarantees. Another reason is so that future development can continue in QA without affecting the production service.


 * Issues. Other tasks have had higher priority (and funding). However, with the requirement for Adelaide to run a copy of the AVH portal frontend, it would be desirable to have a separate copy of the backend running in production.


 * Resources available. Rex Croft is available to perform the promotion to production, when the task is made a priority.


 * Resources needed. 3GB of space on the production Oracle server. MySQL installed on production. BioCASE and required libraries installed on production. Data transfer jobs created to transfer new records to production as well as to QA. Arrange access through the Department's firewall so that external AVH instances can contact the production BioCASE.


 * Start time. Not yet determined.


 * Completion time. I estimate 3 days work. Updates to systems have to be checked into our local code change control system.


 * Notes. I have already spent over 2 months on our AVH provider system. The bulk of that time was spent writing the code that maps the Texpress specimen database fields to the ABCD schema, and the data conversions required to standardise them. And then working with SAPAC/eResearch to get BioCASE to transfer 600,000 records to them without destroying the performance of our QA computer.

BRI

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

CANB

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

CHR

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

DNA

 * Project title. Redevelopment of HOLTZE Specimen Database and Implementation of BioCASE


 * Description. Move HOLTZE Specimen Database to Oracle 10 and web enabled. Development and population of new fields for compatibility with AVH MoU and HISPID5. Test BioCASE in the same test environment concurrently with HOLTZE user testing. Remap AVH MoU/HISPID5 fields in BioCASE.


 * Background. Redevelopment of the HOLTZE Speciemen Database commenced February 2008 to move to Oracle 10 from 8.05 (requirement of a Departmental initiative). Current situation was BioCASE apparently does not operate with Oracle 8.05 and was sitting on an old, risky server. Northern Territory Herbarium also requires advanced functionality built into the application such as mapping tools and reporting operations. BioCASE Provider was installed in 2007 and MoU fields mapped. However, DNA data continues to be provided to the AVH cache via regular data dumps until the re-developed database is in production.


 * Issues. Uncertainty of who is responsible to test BioCASE and re-map fields. Presently aiming to determine whether Department of Natural Resources Environment the Arts and Sport (NRETAS Spatial Data & Mapping group) OR programmers responsible for HOLTZE re-development through Department of Planning and Infrastructure (DPI) are responsible.


 * Resources available. User testing of HOLTZE is a current priority (Donna Lewis full time & Herbarium Staff part time). Finalising the database is also a priority of the contracted programmers and is anticipated for production February/March 2009. Once in production, DNA can work towards implementing BioCASE.


 * Resources needed. Quote for scope of works to implement BioCASE from contracted programmers (DPI).


 * Start time. February 2008


 * Completion time. February/March 2009


 * Notes.

HO

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

MEL

 * Project title. BioCASE implementation and maintenance training and purchase of a new web server


 * Description. Training for Niels Klazenga (Programmer, Information Services) and Alison Vaughan (Collections Information Officer) in BioCASE implementation and configuration.


 * Background. MEL is currently providing data dynamically to the AVH through a BioCASE provider. We will move to a new herbarium management system at the end of 2009, and a new BioCASE provider will need to be configured for the new data model. Implementation of a TAPIR provider has so far been unsuccessful.


 * Issues. Although MEL has a BioCASE provider installed and delivers data dynamically to AVH, the BioCASE provider was installed and configured by Peter Neish (who is no longer on staff) and is poorly understood by current staff. There is an urgent need for training in the operation of the BioCASE provider.


 * Resources available. Programmer (Niels Klazenga) and Collections Information Officer (Alison Vaughan)


 * Resources needed. Training for MEL staff in the implementation and maintenance of the BioCASE provider. MEL also needs a new web server to ensure that we can dynamically deliver data to the AVH in a robust way.


 * {| class="wikitable"

! Estimated cost
 * BioCASE training – two days (based on estimated rate of $1500 per day)EPI || $3,000
 * Travel, accommodation and expenses (based on ATO rates for 2008-09) 	|| $2,350
 * Web server	|| $8,000
 * Total cost	|| $13,350
 * }
 * Web server	|| $8,000
 * Total cost	|| $13,350
 * }
 * }


 * Start time.


 * Completion time. Prior to the release of AVH3.0.


 * Notes.

NSW

 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

PERTH

 * Project title. Implementation of new web server.
 * Description. Specification, purchase, install and configuration of unix box and software for a new DEC Science Division web server.
 * Background. The new server will include a number of web services including a BioCASE server and consequentially an AVH feed.
 * Issues. For over 12 months it has not been possible to add new hosts to PERTH's current server because system resources on the disk, particularly hard disk space, are too finite. Our departmental IT group recommended against installing additional aplications for this reason, and this has prevented us from implementing PERTH's BioCASE web service.
 * Resources available. The server has been purchased and awaiting installation and configuration by an external consultant managed by Ben.
 * Resources needed. Quotes for these services range up to $8000.
 * Start time. Best case scenario is that it is a two-day job that can be done in the 1st week of December. Worst-case is January 2009.
 * Completion time. Once the server is in place and configured, there is perhaps another two days work involved to get the AVH BioCASe feed fully functional. To be in place by the end of December 2008.
 * Notes.

= Other applications =


 * Project title.


 * Description.


 * Background.


 * Issues.


 * Resources available.


 * Resources needed.


 * Start time.


 * Completion time.


 * Notes.

= Project template =


 * Project title. A concise informative title for the project.


 * Description. A short sentence or two describing the project.


 * Background. A short sentence or two describing the background.


 * Issues. A short sentences or two about issues surrounding this project.


 * Resources available. Resources (e.g. staff) currently available to this project.


 * Resources needed. Addition resources (e.g. contracts, etc.) required to complete project.


 * Start time. Time project is able to start.


 * Completion time. Time project is estimated to complete.


 * Notes. Any additional or explanatory notes.