Changes between Version 25 and Version 26 of Centre Registry


Ignore:
Timestamp:
10/31/16 10:10:08 (8 years ago)
Author:
Sander Maijers
Comment:

contents: update to current status based on alpine-django Docker image

Legend:

Unmodified
Added
Removed
Modified
  • Centre Registry

    v25 v26  
    1 == Centre Registry 2.0 ==
    2 A current version is available on https://centres.clarin.eu/ . A staging version on https://staging-centres.clarin.eu/ .
     1== Centre Registry 2 ==
     2A current version is available on https://centres.clarin.eu/ . A staging version shall be deployed https://dev-1-www.clarin.eu/ .
    33
    44=== REST API ===
     
    2929[[TicketQuery(status=accepted|assigned|new|reopened,component=Centre Registry,order=priority,format=table,col=summary|component|priority|owner|reporter)]]
    3030
     31== Deployment using `alpine-django` image project ==
     32
     33See [alpine-django project https://gitlab.com/CLARIN-ERIC/alpine-django].
     34The following data layout is is needed for deployment:
     35
     36{{{
     37/srv/Centre_Registry/                                                                                                                                                                                               
     38├── Centre-Registry-config                                                                                                                                                                                           
     39│   ├── centre_registry_project
     40│   │   ├── __init__.py
     41│   │   ├── settings.py.tmpl
     42│   │   ├── urls.py
     43│   │   └── wsgi.py
     44│   ├── manage.py
     45│   ├── MANIFEST.in
     46│   ├── setup.cfg
     47│   └── setup.py
     48├── database.sqlite
     49└── test_database.sqlite
     50}}}
     51
    3152== The Centre Registry before 2.0 ==
    32 
    33 = Status =
    34 
    35 == Log ==
    36  * 2012-04-11: created ticket queue for Center registry and added some HTML improvements
    37  * 2012-03-14: feedback to RZG developers about XML export improvements
    3853
    3954== Open Tickets ==
     
    4560
    4661== Introduction ==
    47 The centers form the backbone of the distributed CLARIN infrastructure. So far the administration of the center details has been done manually, noting down the entry points and contact information on a web site. In order to streamline the information gathering and to ensure machine accessibility of this data a center registry needs to be built. In this page we specify the requirements for such a registry, in accordance with the CLARIN-D AP3 guidelines.
     62
     63The centres form the backbone of the distributed CLARIN infrastructure. So far the administration of the centre details has been done manually, noting down the entry points and contact information on a web site. In order to streamline the information gathering and to ensure machine accessibility of this data a center registry needs to be built. In this page we specify the requirements for such a registry, in accordance with the CLARIN-D AP3 guidelines.
    4864
    4965== Requirements ==
    50 The center registry is a store for records with information about CLARIN centres.  This document describes the data that it could contain (Data store), the web application for users to view and change the data (Web Interface) and the machine-accessible API (Web Service).
     66
     67The Centre Registry is a store for records with information about CLARIN centres.  This document describes the data that it could contain (Data store), the web application for users to view and change the data (Web Interface) and the machine-accessible API (Web Service).
    5168
    5269== Example files ==
     
    122139To start, the following functions should be available:
    123140
    124 * return a list of all centers (together with a unique center ID): http://foo.eu/rest/centerregistry/centers
     141* return a list of all centre (together with a unique centre ID): http://foo.eu/rest/centerregistry/centers
    125142  * optional parameters: /xml (default, ad hoc xml encoding) or /json
    126   * output: center ID, Basic information fields, if there is at least 1 OAI access point, providing metadata about web services
    127 * return all information about 1 center: http://foo.eu/rest/registry/centers/{centerid}
     143  * output: centre ID, Basic information fields, if there is at least 1 OAI access point, providing metadata about web services
     144* return all information about 1 centre: http://foo.eu/rest/registry/centers/{centreID}
    128145  * optional parameters: /cmdi (default) or /json
    129   * output: all fields in the center record
     146  * output: all fields in the centre record
    130147
    131148Documentation about the webservice: