Timeline for answer to Define a RESTful API for creating/updating other resource definitions? by FrustratedWithFormsDesigner
Current License: CC BY-SA 3.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 3, 2017 at 22:56 | history | edited | FrustratedWithFormsDesigner | CC BY-SA 3.0 |
added 4 characters in body
|
| Jan 3, 2017 at 22:38 | comment | added | FrustratedWithFormsDesigner | @Stew: I've added an update that I think might help. | |
| Jan 3, 2017 at 22:37 | history | edited | FrustratedWithFormsDesigner | CC BY-SA 3.0 |
added 749 characters in body
|
| Jan 3, 2017 at 22:31 | comment | added | user92338 | That said, I'm not saying this is the best idea, just that it is presently a requirement. | |
| Jan 3, 2017 at 22:30 | comment | added | user92338 | I totally agree re: authorization and change tracking. We have those things nailed down. In order: 1. Why? We are building a system for analysts to create, store and update arbitrary datasets. These have a structure that changes from year to year. New ones are added and the analysts want to be able to add and change them. 2. The clients are the same analysts (this is an in-house system), using ETL tools; they expect the change. 3. Stored in a JSON document-based backend with complex schema-specific revisioning. 4. Yes, but this will be easier than our present approach. | |
| Jan 3, 2017 at 22:13 | history | answered | FrustratedWithFormsDesigner | CC BY-SA 3.0 |