vivo_home/api/rest/{version}/events

[chenejac]

Describe the solution you'd like The endpoints for CRUD operations over events should be defined by using Dynamic API ontology.

• GET vivo_home/api/rest/{version}/events
• GET vivo_home/api/rest/{version}/events/{uri}
• GET vivo_home/api/rest/{version}/events/{uri}/subevents
• POST vivo_home/api/rest/{version}/events
• PUT vivo_home/api/rest/{version}/events/{uri}
• DELETE vivo_home/api/rest/{version}/events/{uri}

The JSON format for description an event should be supported with the following structure:

{
  "uri" : "http://localhost:8080/vivo/individual/n7431",
  "type" : "http://vivoweb.org/ontology/core#Presentation",
  "name" : ["Derrida and the Electracy Conundrum@en_US",  "Derida i zagonetka elektriciteta@sr_Latn_RS"],
  # in some cases also "abbreviation" : "",
  # "startDate" : "",
  # "endDate" :  "",
  # "place" : ""
  "eventVenue" : 
      {
         "uri" : "http://localhost:8080/vivo/individual/n4869",
         "name" : ["17th Annual Conference on Philosophy and Rhetoric@en_US", "17. godišnja konferencija o filozofiji i retorici@sr_Latn_RS"]
       }
}

Additional context

• Some examples are available at https://github.com/chenejac/Vitro/blob/sprint-dynapi-2022-may-demo/home/src/main/resources/rdf/abox/filegraph/continentAPI.n3 aligned with Dynamic API ontology at that moment. Postman can be used for testing. OpenAPI specification (swagger.yml) can be generated. Demo meeting - https://wiki.lyrasis.org/display/VIVO/2022-07-07+-+Dynamic+API+demo+meeting (video record here - https://drive.google.com/file/d/1hOrB8D3tDiTU6TuvnT6HJ1JcclOJp3xm/view?usp=sharing)

• The another useful resource might be n3 files for reporting available at https://github.com/vivo-project/Vitro/tree/dynapi/home/src/main/resources/rdf/dynapiAbox/everytime