You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Agenda:
- Closeout requirements
- Versioning on Disposition Letters (e.g., sending an updated Disposition Letter)
- Just checking - not preventing modification of comments to PI
- "A TTA Group member shall be able to edit the disposition text" p.42 of System Description
- Expand on
- "There shall be a mechanism for a TTA Group member to make the approved Allocation Dispositions public in the archive." p. 42 of System Description
- EVLA Project Creation
- Discussion with DF, MB, Phobos team
- Three databases - Scheduling Block, Source Catalog, Resource Catalog
- Like to have rest APIs to interact but not all have rest APIs (only Scheduling Block has one).
- We need to authenticate
- Currently the API serves XML, we would like json
- Broadly speaking, this suggests
- Work done by NM-OPs to create rest APIs when needed
- NM-OPs Modify current API for json
- Iterate with NM-OPs to define API signatures and understand payload
- Goal of v0.4 project creation
- Minimally: Create a stub service and a frontend UI button that calls a REST API and handles the response
- Service transforms the TTAT Source into the right structure of a Source Catalog Source
- Send transformed Source to API