Skip to content

Skosmos 1.7

Compare
Choose a tag to compare
@osma osma released this 20 Jun 11:13
· 26 commits to v1.7-maintenance since this release

The most important improvement in this release is the new Swagger/OpenAPI description of the REST API. It is a declarative, machine-readable JSON description of the API that enables automatically generated API documentation as well as client code generation for various programming languages. Other new features include accessibility improvements, better support for reified definitions, and searching concepts by notation code. There are also performance improvements to the search result page, ability to configure SPARQL request timeouts and the possibility to disable the alphabetical index. These performance-related enhancements make it possible to use even very large vocabularies such as LCSH with Skosmos, though some pages will likely be slow to load.

Translation updates:

  • Updated French translation by Thomas Francart
  • Updated Italian translation by Armando Stellato
  • Updated German translation by Joachim Neubert
  • Updated Norwegian Bokmål translation by Dan Michael O. Heggø

Usability improvements:

  • #416 "The concept is not available in this language" message rephrased
  • #433 Avoid duplicated information when isothes:superGroup and skos:member have both been used
  • #434 Don't reveal hiddenLabels that were used for matching
  • #473 Show vocabulary URI on the vocabulary front page
  • #499 Add "Skip to content" link
  • #500 Add labels/titles for search form elements
  • #501 Add heading for sidebar section

Technical improvements:

  • #452 Make display of skos:notation values optional
  • #456 Search by notation code
  • #458 Support classifying vocabularies by type in vocabularies.ttl
  • #477 Better support for structured/reified definitions
  • #493 Option to disable alphabetical index
  • #508 Smarter getVocabularyFromURI when multiple vocabularies share URI namespace
  • #509 Configurable SPARQL query timeout instead of hardcoded 10 second timeout
  • #524 Introduce SEARCH_RESULTS_SIZE configuration parameter, improving search results loading performance

Documentation improvements:

  • #435 Swagger description of the REST API

Bug fixes:

  • #510 Plugin loading problems with Safari
  • #511 PO metadata shown as translation for empty language tags
  • #512 Generated link to concept scheme not working
  • #513 Blank page and 500 error when URI contains space
  • #514 REST data method doesn't return a 404 when the concept can't be found
  • #515, #531 Member concepts of Array-type collections not shown
  • #532 Groups tab shown on Array-type collection pages
  • #516 REST vocabulary information returns badly formatted languages
  • #518 Redirect to language-specific page doesn't respect BASE_HREF setting
  • #519 Duplicated search results when different vocabularies have different prefLabels for the same concept
  • #522 Vocabulary search limited to 40 results even though there should be more
  • #523 Vocabulary feedback form vocabulary preselection is broken
  • #525 Rest lookup method not working as expected without the lang parameter
  • #526 Global search result language code is empty even though it shouldn't be
  • #528 Mapping links shown in wrong language
  • #529 Labels with special characters not shown in hierarchy view

Code quality improvements:

  • Unit test coverage 88% (was 88% in 1.6)
  • Code Climate score 1.85 of 4, up from 1.77 in 1.6
  • Scrutinizer score 5.95 ("satisfactory"), down from 6.11 in 1.6
  • SensioLabs Insight score 87 of 100 (silver medal), down from 88 in 1.6
  • Codacy overall score B (218 issues), was B (227 issues) in 1.6
  • many other potential bugs and problems fixed based on analysis reports by the above tools

For a more complete list of bug fixes and new features in this version, see issues tagged with the 1.7 milestone.

See the upgrade instructions in the wiki for information about upgrading from earlier versions. There have been some minor changes to config.inc settings in this release, but the default values should work for most users.