Sinopia Known Issues

08/09/2019: update of this page is in progress to reflect Known Issues as of Release 1.0

the Sinopia project board for Work Cycle 1 (through Milestone 4) is here
the Sinopia project board for Work Cycle 2 is here (unprioritized and unfiltered)
see also QA current issues

Linked Data Editor

Browser refresh is required to see new Resource Templates that have been uploaded by another user (or in another session) after you started your session (NOTE: this is not an issue to be fixed; this is the expected behavior given the architecture of the application)
When a revised Resource Template is uploaded, the revised version does not show up in other existing browser sessions, even after a browser refresh. WORKAROUND: hard refresh your browser (hold down shift key and click the refresh icon in your browser) to see the latest list of available templates. (Issue 545)
All Linked Data Editor actions require login. The desired behavior is to be forced to log in only when doing actions that require login (importing resource templates, saving data). (Issue 495)
Sign out button doesn't always sign you out. (Issue 556)

last updated 7/26/19

Using Firefox Extended Support Release browser, the menu to choose a vocabulary from "Select/Change Resource" and "Select/Change Property" buttons is blank (Issue 229)
Clicking the back button in your browser erases your entries. (Issue 158)
We are not adding or updating the list of available vocabularies for "Select Resource" and "Select Property". Workaround: profile creator can manually enter any class or property URI and label into the necessary fields. (Issue 182)
The list of available lookups in "Add Value / URI" dropdown does not update automatically when a new authority is available to Sinopia. (Issue 162)
Not all Share-VDE datasets are available as lookups (Cornell, Stanford, UCSD currently available)
While it's possible to add a default value and/or default URI in a property template with type = resource, Sinopia ignores those, as a single default value for a nested Resource Template does not make sense.