Skip to content

Entity Support in HSLynk

Jump to bottom
Eric Jahn edited this page Feb 16, 2021 · 18 revisions

See also:

HSLynk will support tracking data on definable general concepts and things, as well as specific clients. We'll refer to these general things as "entities". An entity could be a park, a place, a region, a building, an encampment, etc..

Client code example here: https://github.com/hserv/entity-tracking/wiki/How-to-Use-Linked-Data-Platform-APIs-(LDP)-in-Apache-Marmotta

Requirements

  • ability to associate clients with an entity, retroactively as well. Perhaps we could have functionality where one of the counts is converted from just a number to a link to a real client record with identifiers.
  • Should each counted item, if flagged as a person (http://dbpedia.org/ontology/Person), be entered into the system as an anonymous client, that can later have identifiers added, at which point openempi checks it for matches.
  • Read, write, update, delete (CRUD) API accessibility for entities
  • global cross-schema functionality (an entity should be able to have its records located in both the 2015 and 2016 schema.
  • Definable attributes for an entity, so we could track different attributes for a park, as opposed to a building.
    • one common attribute will be latitude and longitude
    • linked open vocabulary name for the entity will be recommended (like a park would be http://dbpedia.org/ontology/Park or https://schema.org/Park), so the rest of the world can figure out what the entity is.
      • We want the administrator to be able to manage/add to the available names that users will see, however, we want to manage at a top level what terms are being used, to avoid a broad use of terms. Linked Data does have the ability to mark one term as "equivalent-to", which does avoid the need for too much close management of terms: just pick from existing vocabularies and they are already all related as equivalents, or subsets of one another.

Design

  • RDF in the form of JSON-LD will store the triple relationships. Subject (Entity) - Verb (relationship) - Direct Object (item tracked)
  • standard metadata like "date updated" will be tracked for all entities
  • surveys can be linked only to existing entities, not retroactively linked
  • role based access control to entity creation to avoid duplicate entities, data quality problems, etc.

Clone this wiki locally