Date
Attendees
Erika Kim
- Rajesh Thangudu
Goals
Clarification of following details:
- Decouple the API calls for Embargo Date from the new Data Use Agreement development.
- Configure the language currently in PDC portal and implement this API for CR’s.
- Document in detail the expected behavior for these API calls from a user perspective.
Discussion items:
- Decouple the API calls for Embargo Date from the new Data Use Agreement development- Yes. This will be taken care of.
- Details of API call: For every API call, we send a new input parameter and user has to provide a True/False value. Based on this input, the response is presented. (details described in an earlier bi-weekly call 12/2/2020, by Michael Holck)
Rajesh's ppt attached here: Enforcing DUA Acceptance in Public APIs.pptx
- Essential communications to ISB for following changes to proactively accommodate PDC changes in the beginning of a Sprint (this will provide 2 weeks at a minimum):
- API related changes and the error message link to the portal, which will be placed under the DUA tab.
- The expired embargo dates have to replaced by N/A, which will break existing code.
- We can communicate via Help and Slack channels, Discussion forums.
- Erika’s request: Can we update the Release version detail google doc to an HTML format for easier viewing?
Rajesh - It can be done but it be helpful to understand the use case for this request and Erika will get that information.
