Difference between revisions of "Hackathon 2013/UseCases"
From TaxonWorks Wiki
(→Implementation plan and milestones) |
(→Implementation plan and milestones) |
||
Line 60: | Line 60: | ||
** 3i | ** 3i | ||
* Develop data exchange with other applications | * Develop data exchange with other applications | ||
+ | ** GBIF | ||
+ | ** ZooBank | ||
+ | * New functionality | ||
+ | ** Collection data for Illinois Natural History Survey | ||
+ | ** Nomenclature codes other than zoological |
Revision as of 09:53, 1 October 2013
Contents |
Members
- Daisie Huang
- David Eades
- Marilyn Beckman
Topics to be covered
- Use cases, identify types of users and what we must deliver.
- Define implementation plan and milestones.
- Map imports from Species Files, MX and 3i into TaxonWorks.
Use cases
- Taxonomists
- Starting point for research
- Existing hierarchy with nomenclatural data
- References to relevant literature
- Added information: specimen data, images, sound recordings
- Assistance during research
- Generate private copy with relevant scope
- Add data in database
- Manage characters including molecular
- Handle OTUs in flux
- Export text to drop in manuscript
- Upon publication
- Merge private copy into public database
- Starting point for research
- Data aggregators
- Export data to Catalogue of Life and ITIS
- Develop data exchange with GBIF, ZooBank, others
- Web service clients
- Requests for hierarchy
- Inquiries about status of names
- Participate in attempts to resolve conflicts with Catalogue of Life Piping Tool
- General public
- Display data in user friendly form
- Collections
- Illinois Natural History Survey
Implementation plan and milestones
- Proof of concept, all data to be discarded
- Create basic tables
- Import taxonomic hierarchy from Plecoptera Species File
- Develop user interface
- Import taxonomic hierarchy from Embioptera Species File
- Add log on with levels of access and saved user data
- Enable editing
- Handle citations including authors and publication data
- Handle images
- Add anything else required for LepIndex
- Enforce compliance with Code of Zoological Nomenclature
- Add anything else required for Universal Chalcidoidea Database
- Import LepIndex
- Import Universal Chalcidoidea Database
- Complete functionality required for existing databases
- Handle specimen data
- Handle character data
- Provide keys
- Verify that all essential data from existing databases can be handled
- Import all existing databases
- Species Files
- MX
- 3i
- Develop data exchange with other applications
- GBIF
- ZooBank
- New functionality
- Collection data for Illinois Natural History Survey
- Nomenclature codes other than zoological