Difference between revisions of "Library Usage Instructions"

Revision as of 17:52, 18 September 2013

Add a Resource to the Library

• Link to add a resource - http://knoesis.wright.edu/lib-manager/ (This interface requires a login. Please contact Kno.e.sis Web Support in case you do not have a login/have lost your login)
• Once Logged in, you would see following 4 options -
  • Publication Resource - To enter any kind of publications (Conference Paper, workshop paper etc)
  • Person Resource - To enter information about a person to the RDF store
  • Other Resource - To add a Demo,Dataset, Service Resource
  • Add Project - Add a project name and its URL (This will automatically get added to the selectable list of projects/ Add a project
• Please read the instructions on each of the forms carefully before adding your resource
• Whenever you see an ADD button next to a input field please make sure you enter your data and PRESS ADD. Now you should see the item below. You can now add another item to the same box.
• You should see a message on submitting the form which would say “Publication added successfully!!”.

Edit a Resource in the Library

• In order to change some information in a resource you would have to use the edit interface.
• Start with a resource in the library. As an example http://knoesis.wright.edu/library/resource.php?id=780
• Now click on the link “Edit this page”. You would see 2 buttons
  • Edit_Entry
    • Login is required for this functionality
    • Will show all the information for this resource to be edited
    • You should see a message on submitting the form which would say “Publication edited successfully!!"
  • Delete_Entry
    • Login is required for this functionality
    • Will delete all the triples from the RDF store for this resource
    • You should see a message on submitting the form which would say “Publication deleted successfully!!”

Important Note

• For all the forms after submission please click the link “Jump Reload To Library” in order to see the changes in the front end at http://knoesis.wright.edu/library
• It might happen that your browser might cache the page http://knoesis.wright.edu/library and hence you would not see the new resource added. It is better to use the a different browser in such a case.

Other Important Information About Library Code

• We used forms for adding data/records to the database. The forms were built using JSP. On submit data was converted to RDF using JENA and was written to the database (I think we were using RDF Sesame version 2.4.1).

• The main page (Simile exhibit) requires the data to be in Exhibit JSON format. In order to convert RDF data (stored in the database), we used simile babel service (http://service.simile-widgets.org/babel/)

• The problem with Simile exhibit is that it loads all the data in the JSON at once. This overloads some browsers like Internet explorer. In order to over come this issue Ajith wrote some scripts that would create JSON - smaller chunks of data (i think by reading the big JSON converted using babel).

• The other pages (individual records E.g - http://knoesis.org/library/resource.php?id=1690) are PHP pages, that get all their content from the JSON itself.

Questions About LIbrary Code

So here are some high level steps - 

1. We used forms for adding data/records to the database. The forms were built using JSP. On submit data was converted to RDF using JENA and was written to the database (I think we were using RDF Sesame version 2.4.1).

2. The main page (Simile exhibit) requires the data to be in Exhibit JSON format. In order to convert RDF data (stored in the database), we used simile babel service (http://service.simile-widgets.org/babel/)

3. The problem with Simile exhibit is that it loads all the data in the JSON at once. This overloads some browsers like Internet explorer. In order to over come this issue Ajith wrote some scripts that would create JSON - smaller chunks of data (i think by reading the big JSON converted using babel).

4. The other pages (individual records E.g - http://knoesis.org/library/resource.php?id=1690) are PHP pages, that get all their content from the JSON itself.

Recommendation -

1. If possible and if time permits I would recommend moving away from Simile Exhibit. The user group is not very active, the system is buggy and very difficult to work with (it needs JSON is a specific format which means the ontology needs to be very simple to be able to convert JSON and rendered on UI). Naveen suggested using http://flamenco.berkeley.edu/ (Abzooba used it for an internal product) and was very happy with the tool

2. Would also recommend moving away from RDF Simile. Great database back in the days but has the same issues as 1 with the newer versions. Allegrograph, Stardog, Virtuoso are better choices (ordered by popularity)