https://github.com/dissco/machine-annotation-service-template

Boilerplate code to facilitate development of machine annotation services for DiSSCo

https://github.com/dissco/machine-annotation-service-template

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.1%) to scientific vocabulary
Last synced: 4 months ago · JSON representation

Repository

Boilerplate code to facilitate development of machine annotation services for DiSSCo

Basic Info
  • Host: GitHub
  • Owner: DiSSCo
  • License: apache-2.0
  • Language: Python
  • Default Branch: main
  • Homepage:
  • Size: 24.4 KB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 1
  • Open Issues: 1
  • Releases: 0
Created over 1 year ago · Last pushed 12 months ago
Metadata Files
Readme License

README.md

Machine Annotation Service Template

Thank you for your interest in developing Machine Annotation Services (MASs) for DiSSCo!

This repository contains template code to facilitate development of MASs. For more information, see our MAS Developers Guide You can find example MASs on our GitHub

Getting Help

Creating issues in this repository is the best way to receive a quick response from the DiSSCo development team.

Using This Repository

This repository is intended to be forked and used as a template for the development of MASs. The annotation package contains code that will format resulting calculations to the openDS annotation model. Two templates are provided: a default template and a batch template. Use the batch template if you wish to support batch operations. \ Supporting batching may result in lower computational demand and reduce workload for the MAS and associated systems, but it requires careful work to set up. More information can be found on our wiki. If your MAS does not support batching, the default template is more suitable.

Kafka Message

Messages are sent between DiSSCo and MASs using Kafka, an asynchronous event messaging platform.

The incoming message will be in the following format: { "object": { ... }, "jobID": "8a325743-bf32-49c7-b3a1-89e738c37dfc", "batchingRequested": true } Where object is the Digital Specimen or Digital Media in openDS, jobID is a UUID that must be passed back to DiSSCo, and batchingRequested is an optional parameter indicating that the user has requested batching on the scheduled annotation. A MAS must be properly configured to batch annotations. See the wiki entry for more information on batching annotations.

Data Model

The following table contains references to relevant schemas and a human-readable Terms reference.

| Resource | JSON Schema | Terms Site | |----------------------------|------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | Digital Specimen | Schema | Terms | | Digital Media | Schema | Terms | | Annotation Event to DiSSCo | Schema | Terms (Note: contains terms computed by DiSSCo as well as the MAS) |

The resulting message back to DiSSCo must comply to the Annotation Event to DiSSCo schema.

Owner

  • Name: DiSSCo
  • Login: DiSSCo
  • Kind: organization
  • Email: info@dissco.eu
  • Location: Europe

Distributed System of Scientific Collections - pan-European Research Infrastructure. Updates on DiSSCo and natural science collections

GitHub Events

Total
  • Watch event: 1
  • Delete event: 1
  • Push event: 5
  • Pull request review event: 3
  • Pull request review comment event: 2
  • Pull request event: 3
  • Fork event: 1
  • Create event: 2
Last Year
  • Watch event: 1
  • Delete event: 1
  • Push event: 5
  • Pull request review event: 3
  • Pull request review comment event: 2
  • Pull request event: 3
  • Fork event: 1
  • Create event: 2