dev:meetings:future_of_staff_client
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:meetings:future_of_staff_client [2013/01/25 17:49] – [Agenda] add idea gmcharlton | dev:meetings:future_of_staff_client [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 7: | Line 7: | ||
* 18:00:00 Wednesday, February 6, 2013 in UTC | * 18:00:00 Wednesday, February 6, 2013 in UTC | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
===== Agenda ===== | ===== Agenda ===== | ||
* Do we still need a staff client? | * Do we still need a staff client? | ||
* Go entirely web-based? | * Go entirely web-based? | ||
+ | * local sqlite db for client | ||
+ | * scheduled uploads to main db at intervals | ||
+ | * client-side data checking | ||
+ | * no direct manipulation or update of data by staff-client user. | ||
* Have a minimal staff client for things like label printing? | * Have a minimal staff client for things like label printing? | ||
- | * Move as much as possible to chrome | + | * Move as much as possible to chrome |
* perhaps even including fieldmapper metadata? | * perhaps even including fieldmapper metadata? | ||
* Pro: reduce latency and network traffic due to loading staff client UI elements | * Pro: reduce latency and network traffic due to loading staff client UI elements | ||
Line 21: | Line 29: | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
+ | * [[http:// | ||
+ | * Objective third-party performance analysis to identify bottlenecks in the system. Future decisions on changes to staff client or other pieces of the Evergreen architecture could be based on evidence from this analysis. (proposal by Kathy Lussier) |
dev/meetings/future_of_staff_client.1359154171.txt.gz · Last modified: 2022/02/10 13:34 (external edit)