Release notes – 1st Release

The first release of ALIADA was finished in September (ALIADA Beta version). A set of usability tests were performed by the museums, librarians and IT developers from the partners in the Consortium. The partners responsible for that monitoring assessed the results and provided the requirements for the first release. Therefore, technical partners added minor bugs and urgent improvements to the workflow before launching the first release of ALIADA.

Here are the main fixed bugs, workflow improvements and data model changes included in ALIADA v.1.0.

FIXED BUGS

• Don´t allow to delete the current user.
• Passwords are now encrypted for greater security.
• When RDF conversion started, it was not possible to view the select to change the profile or the graph.
• Disable some navigation buttons when they are not allowed and highlight the most important ones in each screen.
• Don´t allow to change the path in the server.

NEW FEATURES

• Now, it´s possible to upload more than a file. Uploaded files are listed and the user can select which file will be processed.
• Allow user to select the graph or dataset to wich generated triples will be added.
• Allow to clean the graphs of the user´s institution.
• AJAX call to gather the information about the status of the RDF conversion, linking and URI creation processes.
• User interface in Spanish and English.
• Users can select their institution.
• A 'breadcrumb' trail has been added to the screens.
• New options to close session and access to the user manual.
• Allow to view profiles and templates without editing them.
• Files validation.
• RDF-izer of MARCXML (Bibliographic records) and LIDO.
• Use of graphical elements to display the status of the different processes while they are running.
• Linking to following datasets: Europeana, BNB, BNE, Freebase, Dbpedia, NSZL, Geonames and MARC Code Lists.
• Linked data server creation over Virtuoso triple store + SPARQL endpoint + dereferencing URIs.
• Linked dataset validation: through a number of SPARQL queries.

DATA MODEL CHANGES

• Every user is now related to an institution (one user belongs to one institution), but one institution can have several users.
• A new table called 'graph' was created to store the information about the Virtuoso´s graph to which the triples generated by the RDFizer will be added. Every graph is related to an institution, but one institution can maintain several graphs at the same time. In this way, an institution can save MARC records from the library system in a graph, and LIDO records from the museum system in another graph.