Changes between Version 25 and Version 26 of Centre Registry
- Timestamp:
- 10/31/16 10:10:08 (8 years ago)
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 == 2 A current version is available on https://centres.clarin.eu/ . A staging version shall be deployed https://dev-1-www.clarin.eu/ . 3 3 4 4 === REST API === … … 29 29 [[TicketQuery(status=accepted|assigned|new|reopened,component=Centre Registry,order=priority,format=table,col=summary|component|priority|owner|reporter)]] 30 30 31 == Deployment using `alpine-django` image project == 32 33 See [alpine-django project https://gitlab.com/CLARIN-ERIC/alpine-django]. 34 The 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 31 52 == 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 improvements37 * 2012-03-14: feedback to RZG developers about XML export improvements38 53 39 54 == Open Tickets == … … 45 60 46 61 == 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 63 The 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. 48 64 49 65 == 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 67 The 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). 51 68 52 69 == Example files == … … 122 139 To start, the following functions should be available: 123 140 124 * return a list of all cent ers (together with a unique centerID): http://foo.eu/rest/centerregistry/centers141 * return a list of all centre (together with a unique centre ID): http://foo.eu/rest/centerregistry/centers 125 142 * optional parameters: /xml (default, ad hoc xml encoding) or /json 126 * output: cent erID, Basic information fields, if there is at least 1 OAI access point, providing metadata about web services127 * return all information about 1 cent er: 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} 128 145 * optional parameters: /cmdi (default) or /json 129 * output: all fields in the cent errecord146 * output: all fields in the centre record 130 147 131 148 Documentation about the webservice: