Design Document
From Species File Help
(Difference between revisions)
(Suggestion of possible higher level categories) |
|||
Line 14: | Line 14: | ||
***** {Some category} | ***** {Some category} | ||
** '''Developer''' | ** '''Developer''' | ||
+ | |||
+ | |||
+ | == Possible Higher Level Categories - Names are there as placeholders rather than my lobbying for or against and deserve more thought. == | ||
+ | |||
+ | *Programming (Background on the data architecture and underlying development environment, data tables and more) | ||
+ | **Table relationships | ||
+ | **Table structure | ||
+ | **Access levels | ||
+ | *Administration | ||
+ | **Edit log | ||
+ | **Object id's | ||
+ | **Secure functions | ||
+ | **Restricted taxon changes | ||
+ | *Managing users | ||
+ | *Lists | ||
+ | **List of Species Files | ||
+ | **List of Test Programs | ||
+ | **List of video tutorials | ||
+ | **List of (biodiversity informatics) acronyms (GBIF, TDWG, LSIDs) | ||
+ | *Public | ||
+ | **(see manual) | ||
+ | *Biodiversity informatics community resources | ||
+ | **Biodiversity Heritage Library | ||
+ | **Biodiversity Collections Index | ||
+ | **GBIF | ||
+ | *Editing:Overview [The primary means of working with data - kind of a wastebasket category) | ||
+ | **Taxon pages | ||
+ | ***nomenclator | ||
+ | ***external links | ||
+ | ***scrutiny | ||
+ | ***ecology | ||
+ | ***LSID's | ||
+ | **Specimens | ||
+ | ***primary types | ||
+ | ***repositories | ||
+ | **Media types | ||
+ | ***Images | ||
+ | ***Sounds | ||
+ | ***Videos | ||
+ | ***PDFs | ||
+ | **Distributions and Maps | ||
+ | ***TDWG area maps | ||
+ | ***Google maps | ||
+ | ***Faunal lists | ||
+ | **References | ||
+ | ***Citations | ||
+ | ***Publications | ||
+ | ***Authors | ||
+ | **People | ||
+ | **Test Programs | ||
+ | **Data source | ||
+ | **Keys | ||
+ | **Import and export | ||
+ | **Fossils and extinct taxa | ||
+ | **Search functions |
Revision as of 16:43, 27 March 2012
Id propose outlining the basic hierarchy like so:
The bold words will be the page name.
The bit in [] just a note as to what it represents (not shown else). {} is a suggestion/something waiting to be filled out.
just a demo here, not meant to be actual organization:
- Manual [We anticipate multiple different types of manuals]
- SpeciesFile [We can anticipate multiple "products" from SF]
- Web [Particular to the web front end]
- {Some category}
- Web [Particular to the web front end]
- Developer
- SpeciesFile [We can anticipate multiple "products" from SF]
Possible Higher Level Categories - Names are there as placeholders rather than my lobbying for or against and deserve more thought.
- Programming (Background on the data architecture and underlying development environment, data tables and more)
- Table relationships
- Table structure
- Access levels
- Administration
- Edit log
- Object id's
- Secure functions
- Restricted taxon changes
- Managing users
- Lists
- List of Species Files
- List of Test Programs
- List of video tutorials
- List of (biodiversity informatics) acronyms (GBIF, TDWG, LSIDs)
- Public
- (see manual)
- Biodiversity informatics community resources
- Biodiversity Heritage Library
- Biodiversity Collections Index
- GBIF
- Editing:Overview [The primary means of working with data - kind of a wastebasket category)
- Taxon pages
- nomenclator
- external links
- scrutiny
- ecology
- LSID's
- Specimens
- primary types
- repositories
- Media types
- Images
- Sounds
- Videos
- PDFs
- Distributions and Maps
- TDWG area maps
- Google maps
- Faunal lists
- References
- Citations
- Publications
- Authors
- People
- Test Programs
- Data source
- Keys
- Import and export
- Fossils and extinct taxa
- Search functions
- Taxon pages