Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Description of Steps of an Edit

Step 1. Getting the link to the edit  


B) if you will be deploying the system for the first time and  starting with an empty database, you would update vivo-core-1.5-annotations.rdf to specify that the property has a custom form using the vitro:customEntryFormAnnot property.

 2Step 2. Generating the EditConfiguration  

When the user clicks the link, the client browser requests the URL of the edit link which will be to the EditRequestDispactchControll.  That servlet will set up all that is needed in the session for the edit and respond with the HTML form.  A custom form is setup by the EditConfigurationGenerator which has the sole purpose of making an EditConfiguration object. The EditRequestDispatchController will run getEditConfiguration() on the EditConfigurationGenerator to create the EditConfiguration. The EditConfiguration object has properties to define the characteristics of the edit. The EditConfiguration will specify the FreeMarker template for the form, and the server side instructions for validating and processing the submitted result of the HTML form.  The EditConfiguration may also have the subject, predicate and object of the requested and instructions for processing the edit. When authoring a custom form, a central task is the coding of the EditConfigurationGenerator to produce an EditConfiguration that encodes logic of how you desire the edit to happen.  The EditConfigurationGenerator is just a java class that creates an EditConfiguration. 


The EditConfiguration can specify SPARQL queries for existing values for fields of the form.  These are executed as part of the generation of the EditConfiguration.

Step 3. HTML creation by FreeMarker