A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Name | Website | Description | Ready for Testing? | General Impressions/testing notes | Technical Support Requirements | Software type (backend, middleware, framework, complete solution) | Batch Import Support | Batch editing of controlled vocabulary terms | LOD publishing | Advanced search capabilities | Browse capabilities | Local URI support | Data models supported | Collaborative Workflows | API availability | Data visualization | Open Source Software Development Support | SPARQL Endpoint | Ease of Installation for Digital Infrastructure Development | Ongoing support considerations from Digital Infrastructure Development and recommendations | Time to installed | |||||||||
2 | OmekaS | https://omeka.org/s/ | "Omeka S is a next-generation web publishing platform for institutions interested in connecting digital cultural heritage collections with other resources online." | yes | Robust solution. Can import custom vocabularies expressed in rdf/xml. Provides JSON-LD publishing option for vocabulary. Would also allow for public discovery layer, searching and browsing of vocabulary. | Linux, Apache, Mysql 5.5.3+, PHP 5.6 | complete solution | yes, CSV files | some basic metadata editing, may be able to leverage API to accomplish this as well | Can publish data as JSON LD | yes | yes | no | Can load EAC-CPF | Yes | REST API | some mapping functionaity built in | Open source software supported by the Roy Rosenzweig Center for History and New Media | no | Easy to install and support | minimal | ||||||||||
3 | xEAC | https://github.com/ewg118/xEAC | Beta software, used by the American Numismatic Society | No | Not investigated - Proved to be too difficult to install in our sandbox environment | Apache Tomcat, Oberon (http://www.orbeon.com/), Solr, eXist (http://exist-db.org/exist/apps/homepage/index.html) | Limited support for RDF, SNAC ontology, CIDOC-CRM | EAC-CPF | KML serialization | One developer's project | Was unable to install it fully. I got it to a stage that allowed for some kind of customization, but was not able to get a .war file for eXist even after following several examples of how I was supposed to go about it. The projects that xEAC relies on have changed too much. | ||||||||||||||||||||
4 | Apache Jena | https://jena.apache.org/ | "A free and open source Java framework for building Semantic Web and Linked Data applications." | Concerns about development time with this framework | Not investigated, but keep in mind if we have more development support in the future | Java | framework | RDFS, OWL | RFF API | Apache Software Foundation | ARQ for SPARQL 1.1 available | ||||||||||||||||||||
5 | TemaTres | http://www.vocabularyserver.com/ | "an open source vocabulary server, web application to manage and exploit vocabularies, thesauri, taxonomies and formal representations of knowledge." | Yes | Good for simple vocabularies. Additional granularity could be accomplished by putting more information in notes and meta-terms, and/or adopting custom URL scheme to contain additional elements of descriptive information about our vocabulary. | Apache, PHP, MySQL (or Postgres, Oracle, etc) | complete solution | Simple method for batch import for names only. Would then need to edit names individually to have additional information that we've already developed. | Only available through find and replace operations? | Suports serialization in multiple formats such as: DC MADS SKOS-Core VDEX XTM Zthes JSON JSON-LD | simple advanced search form | yes | There might be some functionality with additional plugins such as https://code.google.com/archive/p/tematresvisualvocabulary/ | GNU General Public License version 2.0 (GPLv2) | Yes | * Simple PHP-based app * Minor tweaks and updates probably relatively easy. * Most comments in the code aren't in English * A bug in the code caused installation instructions * Required special config options to be turned on to create its DB in MySQL. These may have been turned on by default when the app was first written, but are no longer the case today (although the code doesn't appear to be that old) | |||||||||||||||
6 | TMP2 | http://athenaplus.thesaurus.condillac.org/ | vocabulary management tool used by Europeana. It doesn't look like it is something that we could really install or test | no | Not investigated - also website for thesarus doesn't currently resolve in August 2017 | ||||||||||||||||||||||||||
7 | Protege (hosted by Stanford or desktop application) | http://protege.stanford.edu/ | "A free, open-source ontology editor and framework for building intelligent systems. Protégé is supported by a strong community of academic, government, and corporate users, who use Protégé to build knowledge-based solutions in areas as diverse as biomedicine, e-commerce, and organizational modeling." | no | Not investigated - do not need OWL for our project | Hosted solution at Stanford, can also be installed locally with: Tomcat (or some other servlet container) mongoDB - used to store different WebProtege configuration data webprotege.war file | backend | OWL imports supported | Upload and download formats available (according to github documentation): RDF/XML, Turtle, OWL/XML, OBO, and others | Different user configuration options are available: https://protegewiki.stanford.edu/wiki/WebProtegeLayoutConfig | yes | OWL 2 | Yes | Request for REST API on Webprotege github page, but hasn't been implemented | Some visualization options available: https://protegewiki.stanford.edu/wiki/Visualization | Developed at Stanford University | SPARQL querying supported within interface | ||||||||||||||
8 | Skosmos * | http://skosmos.org/ | "Open source web-based SKOS browser and publishing tool" | no | Not tested in sandbox enviroronment after reviewing specifications. Would be useful if our vocabulary was more like a thesarus. | From website: "one or more SKOS vocabularies PHP capable web server SPARQL triple store (we recommend Apache Jena Fuseki with jena-text) HTTP cache (e.g. Varnish) - optional but recommended" | complete solution | yes | no | yes - alphabetical and hierarchical | SKOS | yes | Developed by the National Library of Finland | yes | N/A | N/A | N/A | ||||||||||||||
9 | Collective Access | http://www.collectiveaccess.org/ | "CollectiveAccess is software for describing all manner of things, and allows you to create catalogues that closely conform to your needs without custom programming." | Yes | Highly customizable and configurable, but may take an additional time investment in order to discover if it will work well for the way we are trying to structure our vocabulary. You can define custom vocabularies in Collective Access. Also, the out of the box entity management functions in Collective Access look like they match up well with some of the elements we are wanting to borrow from EAC-CPF. In addition to this, there's integration with external vocabularies like LCNAF and ULAN. | Apache, PHP, MySQL http://docs.collectiveaccess.org/wiki/Requirements | complete solution | This is completed through a spreadsheet config sheet that is uploaded and creates an import profile. You can then import spreadsheets or XML using that import profile. | yes | no | N/A | yes | REST API | Additional consulting help available | no | not difficult to install | |||||||||||||||
10 | Mulgara (not needed if we use Apache Jena) | http://www.mulgara.org/ | "Mulgara is a fast RDF database written entirely in Java." | no | Not investigated | There has only been one small update to Mulgara since 2012, do not investigate as not currently in development | |||||||||||||||||||||||||
11 | OpenRefine (desktop application) | http://openrefine.org/ | "OpenRefine (formerly Google Refine) is a powerful tool for working with messy data: cleaning it; transforming it from one format into another; and extending it with web services and external data." | Will likely use as part of local reconciliation workflows for people who want to reconcile their data against WNAF, but this isn't a complete solution. | Desktop client | middleware | https://github.com/felixlohmeier/openrefine-batch/ - just dropping this script for Open Refine batch work here, since it might come in handy at some point | NA | NA | ||||||||||||||||||||||
12 | Trifacta Wrangler (desktop application) | https://www.trifacta.com/products/wrangler/ | "Trifacta Wrangler brings Trifacta’s breakthrough approach to how data is explored and transformed for analysis to everyone in a free desktop application. Trifacta Wrangler is for any analyst who needs a more intuitive and productive way to discover and manipulate diverse data to fit the format and structure requirements of downstream analytics, visualization and statistical tools." | not applicable for WNAF project | Geared to corporate use cases - not investigated as using Open Refine for reconciliation works for the piece of our project that requires reconciliation. | Desktop client | middleware | commercial tool | |||||||||||||||||||||||
13 | Vitro | http://vitro.mannlib.cornell.edu/, https://github.com/vivo-project/Vitro | "Vitro is a general-purpose web-based ontology and instance editor with customizable public browsing. Vitro is a Java web application that runs in a Tomcat servlet container." | http://vitro.mannlib.cornell.edu/vitroDeploymentGuide.html | Java, Tomcat | ||||||||||||||||||||||||||
14 | RAMP (for eac-cpf authorities work and wikipedia, might not be in scope but putting it here just in case) | https://github.com/UMiamiLibraries/RAMP | "A web-based editor for working with EAC-CPF records and Wikipedia articles. " | no | Not applicable for this project, but noted due to EAC-CPF connection | middleware | |||||||||||||||||||||||||
15 | Controlled Vocabulary Manager | https://github.com/OregonDigital/ControlledVocabularyManager | "Application for managing controlled vocabularies in RDF for Opaque Namespace terms." | no | Tool supports multiple fields per name term, such as type (concept, corporate, personal, title, topic..), label, and a comment field for contextual information. Fields | Ruby 2.0, Vagrant (requires Git, VirtualBox, and Vagrant. Also requires 2 gigs of RAM to be available for the VM which vagrant creates.) | complete solution | yes | yes | yes | Maintained and updated by the University of Oregon and Oregon State University | # Jacob ---- * Rails app * I was unable to deploy due to ignored config files in the project's git repo * Anna is in communication with the devs at Oregon State and may be able to get this data * Despite the problems, I think this could be a really good solution * Seems relatively simple * Uses an gem-based engine approach that should make tweaks to the UI easier * Uses the `devise` gem for logging in users, which can be modded to work with CAS | |||||||||||||||||||
16 | Redis (triple store) | https://redis.io/ | "Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability via Redis Sentinel and automatic partitioning with Redis Cluster." | no | Would require additional development support. Different modules are availbe to extend functionality: http://redismodules.com/ | https://redislabs.com/redis-enterprise-documentation/installing-and-upgrading/hardware-software-requirements/ | backend | yes | https://www.npmjs.com/package/redis-visualize | Open source software with commercial support option | https://github.com/dshafer/sparql-redis-server | ||||||||||||||||||||
17 | Questioning Authority (ruby gem for hydra framework) | https://github.com/projecthydra-labs/questioning_authority | Provides a set of uniform RESTful routes to query any controlled vocabulary or set of authority terms. Results are returned in JSON and can be used within the context of a Rails application or any other Ruby environment. Primary examples would include providing auto-complete functionality via Javascript or populating a dropdown menu with a set of terms. | Assume this is better for querying and autocomplete than the vocabulary maintenence we are wanting for our project | Investigate further if our digital library environment changes to be more compatible with Samvera. Note that we are likely to use this with the data repository, can test then in that context when it is installed. | ||||||||||||||||||||||||||
18 | iQvoc * | https://github.com/innoq/iqvoc | http://iqvoc.net/ "iQvoc supports vocabularies that are common to many knowledge organisation systems, such as: Thesauri Taxonomies Classification schemes Subject heading systems" | account request -iqvoc@innoq.com; sandbox site -http://try.iqvoc.net/en.html | Commas are used to separate distinct terms, so names formatted according to LC NAF will pose problems. This makes it not very well suited to our name authority project. | Ruby on Rails | complete solution for SKOS vocabularies | no | no | Easy way to get representation of concepts in: html rdf/xml rdf/turtle rdf/ntriples | basic advanced search form | yes | system generated URIs | SKOS | Yes, concepts can be locked for editing, and then formally published. | github repository last updated in April 2017 | yes | # Jacob ---- * Rails app * Based roughly on Hydra infrastructure * Installation was easy and straightforward * Could be a good solution | |||||||||||||
19 | ThManager | http://thmanager.sourceforge.net/ | "ThManager is an Open Source Tool for creating and visualizing SKOS RDF vocabularies, a W3C initiative for the representation of knowledge organization systems such as thesauri, classification schemes, subject heading lists, taxonomies, and other types of controlled vocabulary. ThManager facilitates the management of thesauri and other types of controlled vocabularies, such as taxonomies or classification schemes. " | no | Combination of dublin core application profile for thesauri and skos. Might be best suited for a true thesarus with broader and narrower terms, than the type of data associated with personal and corporate names. | Java | complete solution for SKOS vocabularies | yes - can batch import SKOS records | thesarus data can be exported as rdf/xml | yes - a number of viewers are provided: "Alphabetic viewer: It provides the list of thesaurus concepts alphabetically ordered in the selected language. Hierarchical viewer: It provides a tree showing the hierarchical structure of thesaurus concepts. Concept viewer: For a selected concept it shows all the properties allowing additionally the navigation to the related concepts by means of hyperlinks. Search tool: It facilitates search of concepts. The searching process is based on preferred labels allowing the following criteria: "equals", "starts with" and "contains"." | SKOS | Not seeing anything about user management in documentation | Developed by University of Zaragoza, GNU license | ||||||||||||||||||
20 | VocBench | http://vocbench.uniroma2.it/ | "VocBench is a web-based, multilingual, editing and workflow tool that manages thesauri, authority lists and glossaries using SKOS-XL. Designed to meet the needs of semantic web and linked data environments, VocBench provides tools and functionalities that facilitate both collaborative editing and multilingual terminology. It also includes administration and group management features that permit flexible roles for maintenance, validation and publication." | VocBench3 looks more promising but hasn't been released yet as of September 2017. Was slated to be released in July 2017. Public facing documentation for VocBench 3 not yet available (documentation currently in README files of source code). Wait and revisit later if necessary on evaluating this solution. | VocBench3: Required Node.js and npm. Verify that you are running at least node v6.9.x and npm 3.x.x by running node -v and npm -v in a terminal/console window. Older versions may produce errors. Required Semantic Turkey server running. VocBench2: Apache Tomcat, MySQL Ontotext GraphDB installed on a Sesame2 (RDF4J) server (optional, though highly recommended for managing repositories larger than toy examples) | VocBench 3 will support both OWL ontologies and SKOS thesauri | yes | # Jacob ---- * Java-based application * Application failed to load properly on our current standard server environment * Dispite the failure, installation was straightforward, and a version with up-to-date components would most-likely be easy to install and manage technically. * Many of the components are antiquated * Relies on Tomcat6, which is not compatible with our Ubuntu 16.04 servers (Tomcat7 seems to work, but may have unknown bugs) * Uses a product called `Symantic Turkey` which fails to load properly * Load requires `sudo` to write to an unspecified data directory * Load fails to respond to its designated port, even with `sudo` * Currently undergoing an update to version 3 (VB3) * May be a promising option once VB3 is available (estimated release July 2017) * VB3 appears to be actively worked on, the git repository showed quite a bit of usage | |||||||||||||||||||||||
21 | |||||||||||||||||||||||||||||||
22 | |||||||||||||||||||||||||||||||
23 | |||||||||||||||||||||||||||||||
24 | |||||||||||||||||||||||||||||||
25 | |||||||||||||||||||||||||||||||
26 | |||||||||||||||||||||||||||||||
27 | |||||||||||||||||||||||||||||||
28 | |||||||||||||||||||||||||||||||
29 | |||||||||||||||||||||||||||||||
30 | |||||||||||||||||||||||||||||||
31 | |||||||||||||||||||||||||||||||
32 | |||||||||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||||||
36 | |||||||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||||||
38 | |||||||||||||||||||||||||||||||
39 | |||||||||||||||||||||||||||||||
40 | |||||||||||||||||||||||||||||||
41 | |||||||||||||||||||||||||||||||
42 | |||||||||||||||||||||||||||||||
43 | |||||||||||||||||||||||||||||||
44 | |||||||||||||||||||||||||||||||
45 | |||||||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||||||
47 | |||||||||||||||||||||||||||||||
48 | |||||||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||||
100 |