Skip to content
Branch: master
Commits on Aug 13, 2019
  1. Resolved #83 and #84

    sauterl committed Aug 13, 2019
    Added informative sections to the README w.r.t. versioning and styleguide
Commits on Aug 6, 2018
  1. Resolved merge conflicts by using the ours strategy

    sauterl committed Aug 6, 2018
Commits on Aug 4, 2018
  1. Refactored metadata filtering.

    sauterl committed Aug 4, 2018
    Code cleanup and consequent usage of Metadata*Filter objects as
  2. Added required classes for implementation of #63

    sauterl committed Aug 4, 2018
  3. Added GET handler for metadata by id, domain + key

    sauterl committed Aug 4, 2018
    This complies with #64
    A new GET route was added, with the structure
    to serve metadata of a certain object, in a specified domain and with
    given key, designed to have quick access to certain specific metadata.
  4. Added key-based metadata search

    sauterl committed Aug 3, 2018
    This complies with #64
    There is a new post action: /find/metadata/with/:key will retrieve all
    metadata associated with the sent IdList and with the matching key.
    The matching comparison is NOT case sensitive
  5. Added support for domain-specific metadata request

    sauterl committed Aug 3, 2018
    Added a RESTful api handler for domain specific metadata requests.
    This behaviour was mentioned in #64
    The POST request handler works as defined in #64.
    See the classes documentation to know how the GET request works.
  6. Added response header in RESTful API to allow all headers

    sauterl committed Jul 16, 2018
  7. Restored consistency in certain query responses

    sauterl committed May 30, 2018
    The WebSocket and RESTful API now returns the same JSON objects for
     * /find/metadata/by/id
     * /find/objects/by/id
     * /find/segments/by/id
    Each of the corresponding RESTful action handler's now do have the same result
    type as the corresponding WebSocket handlers have.
    The main advantage is that both APIs do now have similar response
    Further, there is a minor advantage in not sending top level arrays: A
    few JSON processors cannot handle such documents and would therefore not
    be able to be used in a cineast context.
You can’t perform that action at this time.