Confirm workflow for web-based editing tool

[torrin47]

This ticket is designed to capture the major requirements/architecture for a web-based editing tool. Per Ana's vision:

Metadata editing vision:

• Web based editor would be used as a light weight editor for non-geo records (POD fields) and geo records (POD fields only)
• Web based editor would also be able to create new non-geo record
• EME used to create new metadata records and to edit geo records beyond POD field

Metadata editing needs to be limited to known stewards, so it should be behind the agency login and recognize EDG authorization groups.
If non-geo records are going to be edited in place, the editor code should probably sit on the edg-intranet server where the raw .json files also sit - that way the server side code could have direct access to the source records, all records from a single owner (in a single json file) could be loaded/edited/updated at once, and the result written immediately to the server without the user needing to download anything. Ideally after the edit, a re-harvest would also be triggered.

The editor tool should follow the EPA metadata technical spec and focus exclusively on non-geo/POD fields.

Users creating brand new files from scratch (without pointing at an existing .json file on the server) would be able to save a copy of the record to their desktop that they could then send to edg@epa.gov for posting to our server.

Users editing existing JSON files would also be able to save a copy of the complete/updated JSON file locally if they wish.

Editing Geo records is more challenging - tool would need to be able to bring source XML to browser, make edits and allow updated XML to be saved locally (not pushed back to the server). User would then be responsible for placing the XML in an appropriate harvest location.

This ticket probably needs to be broken up into smaller tickets.

[torrin47]

This issue was moved to USEPA/EPA_Environmental_Dataset_Gateway#13