Difference between revisions of "Hackathon 2013/UseCases"
From TaxonWorks Wiki
m (→Use cases) |
|||
Line 8: | Line 8: | ||
* Define implementation plan and milestones. | * Define implementation plan and milestones. | ||
* Map imports from Species Files, MX and 3i into TaxonWorks. | * Map imports from Species Files, MX and 3i into TaxonWorks. | ||
− | |||
== Use cases == | == Use cases == |
Revision as of 09:37, 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
- Import LepIndex
- Import Universal Chalcidoidea Database
- Import all Species Files
- Import all MX and 3i databases
- Develop data exchange with other applications