Page History

...

1. DSpace notation for representing generic forms

   1. DTD - https://github.com/DSpace/DSpace/blob/main/dspace/config/submission-forms.dtd

   2. XML example - https://github.com/DSpace/DSpace/blob/main/dspace/config/submission-forms.xml
   3. there is also item submission which is describing steps - https://github.com/DSpace/DSpace/blob/main/dspace/config/item-submission.dtd, https://github.com/DSpace/DSpace/blob/main/dspace/config/item-submission.xml
2. SPARQL Generate library link: https://triply.cc/docs/yasgui/
   1. Main module called Yasgui: has SPARQL editor called Yasqe and result visualizer called Yasr.
      1. Brian note (ex post facto): YASQE is used in VIVO's SPARQL Query admin page
   2. Based on codemirror: https://codemirror.net/ - library to style the editor, deciding from the data input you have.
3. Role management
   1. There has been talk over the years of being able to grant permissions to edit entities based on relationship to editor, e.g.
      1. Head of organization can edit details and working titles within organization (but perhaps not positions and official titles that can only be edited by HR)
      2. PI/Co-PI of grant can edit grant details (but perhaps not certain properties like internal ID or award amount that can only be edited by someone from the research administration)
   2. Would be nice to specify these paths and behavior using ontology instead of code.
   3. Performance of complex rules is always a challenge because they to lead to multiple small queries to triple store to check permissions.  Will need to be appropriately batched/cached to work well with external triple stores.

Action items