Flora writers maintain data in Delta/LUCID keys - how do we avoid them having to maintain information in two places with/while there is no linkage between such a key repository and the eFlora platform?

[ala-bugherd]

http:https://www.bugherd.com/projects/58735/tasks/81

[ben3000]

Having had conversations with staff here, I think it is pretty crucial that the most basic support be enabled initially. Some don't want to maintain their data in one system and are thus happy to separate their profile data and their key data, while others would be quick to use a system that permitted all the data to be maintained in DELTA while permitting import into eFlora.

Example Workflows

User X updates profile descriptions directly in eFlora and separately—perhaps in the same work session—maintains a Lucid or DELTA key project. The same data is thus typed into two separate applications in whatever manner those applications permit.

User Y maintains all data in DELTA or Lucid (data typed once), then runs an export to CSV or some other format and uploads that into eFlora, replacing the descriptions previously provided there.

[RobinaSanderson]

To make this feasible eFlora would need:

1. to move to lucid keys
2. for a lucid key database to be used by the eFlora community to capture keys for taxa
3. the database keys to be exported to the eFora application
4. the keys for a taxon to be concatenated in a standard way to provide a base description (this could populate automatically as per the stub function for distribution and nomenclature)
5. probably would need a facility to enter further description information

Then use case Y above is feasible.