The following is a list of high-level functionality we expect this system to support

[aazaff]

1. Ability to display linked images in database
2. Autosuggest in fields when searching in forms
3. Versioning of all data entries
4. Ability to delete
5. Ability to do filtering logic AND/OR/EXCLUDES etc. on all searches
6. Export data as CSV, PDF, and JSON
7. Search at scale (responsive)
8. Account management and multiple levels of permission
9. Users and Authors are not separate
10. Validation when data is coming -- and support for complex validation rules (i.e. complex logic)
11. Validation needs to be entirely encapsulated within API, not passed to client
12. Migrations scripts need to be treated as one-off and not as re-usable tools
13. As much as possible our download API should build-on the original 1.2 API download functionality https://paleobiodb.org/data1.2/

Preference/Stretch goal

1. Use SQL triggers as much possible over scripts
2. As much as possible our upload API (e.g., POST/PUT/PATCH) should build-on the original 1.2 API upload functionality https://paleobiodb.org/data1.2/

Open Issue

1. Ability to pass array of data in a form to API and accept or reject entire array. We see a lot of complications with this, but they did feel strongly about this in the past?
2. Do we want to use an ORM/OMD?