Release notes – 2nd Release

The second prototype of ALIADA was finished in June. 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 second release. Therefore, technical partners also added minor bugs and urgent improvements to the workflow before launching the second release of ALIADA.

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

FIXED BUGS

• Show the instituion logo and check the upload image went well.
• Some data can´t delete, like profiles, templates...
• Remove RDFizer validation UI.
• Upload files management.
• A correct workflow with any file.
• Workflow for adding another file.
• Workflow for recovery any session file.
• All the new css to improve the user interface.

NEW FEATURES

• User interface in Hungarian and Italian.
• Tool settings UI with tabs.
• Datasets and subsets settings.
• Reload external datasets settings.
• Select a dataset and a subset for the conversion process.
• Clean the graph and the links graph from the subset.
• Link with the selected external datasets UI.
• Check the links for all the selected external datasets.
• Workflow of dataset publication.
• Translation of DublinCore XML and MARC XML Authorities.
• NER (Named Entity Recognition) for some text free elements of the MARC and LIDO records.
• Validation of RDF dataset consistency.
• Ad-hoc linking to some of the listed external datasets , which do not provide a SPARQL endpoint: VIAF, LOBID, Open Library and Library of Congress Subject Headings.
• Show links validation (Ambiguous links and all the links).
• Links disambiguation: the end user can decide which discovered links are acceptable and which ones are rejected.
• Additional URI de-referencing and a web page for the generated dataset.
• Publication in CKAN of the created linked dataset.
• Offer the possibility to update the linked datasets published.

DATA MODEL CHANGES

• DB tables new structure.