Custom Edit form prepopulated with existing values
Samantha-Jane McNally
I would like to be able to edit each row individually using the same custom form I used to enter the values, with the only difference being I would like it to already have the values prepopulated when i launch to edit the row.
Hope this makes sense!
Thanks in advance for your time
stel...@uniroma2.it
Dear Samantha,
the custom forms are always meant as kind of “constructors” for new entities, specifying only the minimum required information (or suggested properties that are non-mandatory to be filled).
Once a resource is created, the locus for editing it is the resource view. The resview, though, can be customized (https://vocbench.uniroma2.it/doc/user/data_view.jsf#customization_of_resourceview ).
Also, as you mentioned tables (a possible view format of custom views), these can be made editable. If your table does not require complex queries (i.e. it only groups 1-hop jumps in the graph) you can use the static vector model and editability comes with no effort. The other mechanism, dynamic and based on SPARQL, is more powerful but requires playing well with pivots in order to perfectly isolate the elements in the table and allow for their editability.
That said, I notice that your properties are zero-hops from the resource being described (that is, the values you need to reach are directly the objects of outgoing triples from the resource you are viewing). Custom views were not thought for that, rather for allowing “look aheads” on values that are farther than mere outgoing triples. What you ask for, in this case, is a further customization possibility for the resource view that reorganizes its content into tables (currently, only creation of custom sections, giving custom labels to properties and a few more options are possible).
Thinking broader, I do not see (but I might miss some point) a need for reorganizing properties into tables, but a asked use case comes to my mind: users familiar with spreadsheet (the classic Excel editing ;-) ) might want to edit not just one concept, rather have a global view of several concepts together. While this could again, demand for a dedicated solution and could be debatable whether this is not too specific to small use cases (I see the immediate advantage for users dealing with small, flat, authority lists, less clear how this improves for large thesauri), I can imagine one way to deal with it:
Create a scheme, say S
Now, for instance, create some concepts and make them top concepts of S. It is important that, in order to use the simple solution with the static vector model, the skos:hasTopConcept is made explicit (you can use the trivial reasoner as normally VB only asserts the inverse triple: skos:topConceptOf) then you can put a table view on the scheme showing all of the properties you said, and bind the table to the property skos:hasTopConcept. In this way, you can see all of the concepts that are bound to scheme S and show also all of their values on the same row. Like I said, I don’t know how much this scales up for very large resources, but if the intent is to provide an excel-like view for small things such as an authority table, that would do it :-)
Kind regards,
Armando
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/dbb3bef9-c54b-4686-aa3d-2586dd8c16b3n%40googlegroups.com.