cmiya
commented
7 years ago Questions/Notes:
How would it work for Snippets?
- Susan pointed out that it would be very helpful to be able to point to the source.
- How would the snippet extracts be generated? Automatically from the URL? Can the user copy and paste a selection?
- Could the user edit the Snippet information and/or add notes?
Autocomplete:
- Where should it get its data? The Virtual International Authority File (OCLC). Shawn suggests that integration with external data sources, while important, might be a future add-on feature. *Assuming that preloaded ontology will supply data for autocomplete.
Deleting Entities:
- When you click on an Edge in edit mode, the edge would be loaded into the editor. Then a delete button would appear alongside the Save and Cancel buttons, so that you could delete the entity.
Saving Work:
- Would be able to do a file download to save work. This way user could save/return to work at a later time without need for authorization/logins, etc.
Auto-Save vs. Persist
- Auto-save: automatically saves when a sucessful drop happens
- Persist: keeps predicates engaged after they've been saved
- This function should work for each of the fields (subject, object and predicate)
- Susan suggests that every time you draw an edge it should flash and read "saving"
Other Notes
- Literal string: i.e. entities not connected into the ontology
- DatatypeProperty: unique to object; the others would always be URIs
- The complexity of this work (and potential for mistakes, especially in auto-save mode) would make it very useful to have an 'Undo' option.
- Loading data from URL
smurp
antimony27
If the user has the right to edit in the current context then...
Expose a toggle (perhaps in the upper left) that looks something like this:
The View mode continues to expose the current behaviour.
When the Edit mode is engaged then a wide single line form is revealed off to the right of the toggle. The form contains three fields:
Subject,PredicateandObject.Behaviour
Savebutton becomes clickablesubjectandobjectnodes would be highlighted and lablled during this period too (similar to when an edge is being hovered over). Until the predicate is established the edge is grey.subjectin the form and while one is dragging a new grey line will be visible to represent the new edge being created. The tail of the line will remain at the subject node and its head will follow the cursor, latching when close enough to the possible object node.objectpredicatefield is set and is set to a predicate which has a range which is a string, date or number datatype then three things happen:objectfield changes to an appropriate widget for that datatypesubjectof the tripleClearbutton is pressed or thepredicateis changed to an ObjectPropertysubjectwhile any label becomes the value of theobject; the value of the label becomes theobjectand the appropriate predicate is shown. If there are multiple triples which are recognized as being labels then the subject-predicate-object-save-cancel-delete section is multiplied, one per triple.autounder the predicate which would cause Save to happen as soon as a successful drop happens -- whereupon thesubjectandobjectwould be cleared but thepredicatewould retain its value. This auto-save behaviour could only be engaged while thepredicatefield had a value and would only be sensible if thepredicatewere an ObjectProperty -- meaning that the object must be a resource rather than a literal data value such as a number, date or string.