Hide Triples From Front End #11
Comments
Sebastiano-G
added a commit
that referenced
this issue
Feb 12, 2024
Updated back-end management for Intermediate Templates inputs: mechanism for creating multiple Records (+ related named graphs) based on different Templates; made them available for corrections and reviews; fixed some DOM-related script. Final visualizations (Explore section) is not available yet. Created an option to make fields hidden. Related mapping behaviours are still to be defined.
Sebastiano-G
added a commit
that referenced
this issue
Feb 14, 2024
#11 : introduced a mechanism to retrieve and save previously added hidden triples while updating a named graph; #10 : introduced the possibility to integrate advanced field types (e.g. Textbox > entity; SKOS vocabularies; etc.) within subrecord forms. Automatic suggestions' visualisation should be improved (i.e., needs to be properly placed within the corresponding section). Moreover, two novel functions have been introduced to either remove entire subrecords or modify them (the latter function is not over yet: advanced fields require further attention)
Sebastiano-G
added a commit
that referenced
this issue
Feb 19, 2024
#11 : removed hidden triples from published records' visualization (app.py); fixed the script for retrieving previously added hidden triples (queries.py, mapping.py); introduced a control algorithm to avoid templates' issues, e.g.: fields can't be both hidden and mandatory (main.js, template.html). #10 : improved graphical visualisation (main.css, main.js); fixed the function for handling multiple inner sub-records
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need the ability to hide triples from the front end, but make sure that they are not deleted from record graphs. This is necessary when there are values that should not be shown to users. Currently, if I import a graph via Blazegraph that contains triples that are not in the model, they are deleted if I edit the record via the back end.
The text was updated successfully, but these errors were encountered: