Changes between Version 2 and Version 3 of CmdiVirtualCollection/Requirements


Ignore:
Timestamp:
05/21/14 13:03:06 (10 years ago)
Author:
Twan Goosen
Comment:

split up requirements section

Legend:

Unmodified
Added
Removed
Modified
  • CmdiVirtualCollection/Requirements

    v2 v3  
     1[[PageOutline(2-4)]]
     2
    13= Virtual Collection Registry: functional requirements =
    24
     
    6567=== Core requirements ===
    6668
    67 
    68    * VC model
     69==== Virtual collection model ====
    6970      * Type
    7071         * Extensional
     
    9899         * (Query profile)
    99100         * (Query value)
    100    * Storage of VC’s
    101       * Relation database backend
    102    * PID assignment
     101====  Storage of VC’s ====
     102Relation database backend
     103
     104
     105==== PID assignment ====
    103106      * Each (published) VCR should be assigned a VCR
    104107      * One or more PID providers
     
    106109         * CLARIN handle has been requested. Server will run at …?
    107110         * !DataCite?? https://mds.datacite.org/
    108    * REST service
     111
     112==== REST service ====
     113
    109114      * /VCR
    110          * GET gets all VC’s (can be filtered using VCRQL (see Protocol))
    111          * POST VC creates a new VC (can be incomplete, e.g. only metadata)
     115         * '''GET''' gets all VC’s (can be filtered using VCRQL (see Protocol.txt))
     116         * '''POST''' VC creates a new VC (can be incomplete, e.g. only metadata)
    112117      * /VCR/{ID}
    113          * GET gets representation of a single VC
    114          * PUT modifies existing unpublished VC
    115          * DELETE deletes existing unpublished VC
     118         * '''GET''' gets representation of a single VC
     119         * '''PUT''' modifies existing unpublished VC
     120         * '''DELETE''' deletes existing unpublished VC
    116121      * /VCR/{ID}/cmdi
    117          * GET a CMDI representation of a single VC
     122         * '''GET''' a CMDI representation of a single VC
    118123      * /VRC/{ID}/URI
    119          * PUT adds an URI to a VC
    120          * POST updates URI
    121    * OAI Provider
     124         * '''PUT''' adds an URI to a VC
     125         * '''POST''' updates URI
     126
     127This is largely in line with [/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/Protocol.txt@522 Protocol.txt]
     128
     129==== OAI Provider ====
    122130      * Provides published VC’s as CMDI
    123    * Web based front-end
     131
     132==== Web based front-end ====
    124133      * Browse public VC’s
    125134      * Browse private VC’s
     
    128137      * Shibbolised
    129138
    130    * Integration into secondary tools
     139==== Integration into secondary tools ====
    131140      * Resource providers (POST/PUT clients)
    132141         * VLO