Closed clarkepeterf closed 2 months ago
@clarkepeterf - I added the LUX environment spreadsheet into the UAT section. Before any environments change we should take a screenshot of the current spreadsheet & then review if the updated spreadsheet is different from the screenshot with accurate updates.
If you have any other ideas for UAT let me know. This is one approach we can use.
Code to grab data version from a document:
fn.head(cts.doc(fn.head(sem.sparql(`
prefix la: <https://linked.art/ns/terms/>
SELECT DISTINCT ?objectIri WHERE {
?objectIri la:equivalent <http://vocab.getty.edu/ulan/500303558> ;
}
`)).objectIri).xpath('/admin/conversion-date')).toString()
There should always be a document(s) equivalent to Yale University in the LUX dataset
@gigamorph I have two questions for you:
Approved by UAT 9/27
Closing as this was implemented and the url works fine.
Problem Description: The LUX Environment Overview Spreadsheet must be updated manually. This means it can be out of date if not updated along with code deployment, or subject to user error when entering data.
Expected Behavior/Solution:
Instead of using the spreadsheet we could create a webpage that interacts with API endpoints in Jenkins deployments or the applications themselves to display the correct info.
Requirements:
/admin/conversion-date
property in the data- [ ] Optional: Include file in each dataset that has a consistent URI?xdmp.version()
Needed for promotion:
- [ ] Wireframe/Mockup - Mike- [ ] Committee discussions - Sarah- [ ] Feasibility/Team discussion - Sarah- [ ] Backend requirements - TBD- [ ] Frontend requirements- TBD- [ ] Are new regression tests required for QA - Amy- [ ] Questions- List of questions for discussions. Answers should be documented within the issue.UAT/LUX Examples:
Note: Green doesn't have the ML code to display versions right now. We don't want to update the code in PRD, so Green will show errors until after the next blue-green switch (on October 1st) when we can update it.
Dependencies/Blocks:
- Blocked By: Issues that are blocking the completion of the current issue.- Blocking: Issues being blocked by the completion of the current issue.Related Github Issues:
- Issues that contain similar work but are not blocking or being blocked by the current issue.Related links:
- These links can consist of resources, bugherds, etc.Wireframe/Mockup:
Place wireframe/mockup for the proposed solution at end of ticket.