|
GEOSS CSR Version 3.2.1: Single Standards/Special Arrangements Association/Multiple Form Registration
March 2, 2014 CSR v3.2.1 combines "Classification" and "Supportive" standards into a single "Standards/Special Arrangements" to associate with the resource to be registered. These "Standards/Special Arrangements" are either optional or mandatory based on "Resource Category" selected. Furthermore, the new version also highlights multi-form registration system for easy navigation and registration of the resource. GEOSS CSR Version 3.2: Remove Service resource type
April 1, 2013 CSR v3.2 removes the "service" type from the Resource Category, and remove the association between component and service. There will be no longer a distinction between Component and Service, and all the records will be combined to be refers as Resources. GEOSS CSR Version 3.1: Consistent metadata model for component and service
Jan. 15, 2013 CSR v3.1 uses ISO19115 metadata model for all resource type. The same registration page, query page and metadata model are implemented for both previous component and service. GEOSS CSR Version 3.0: GeoNetwork-based CSR with ISO metadata model
June 25, 2012 CSR v3.0 uses ISO19115 and ISO19119 for non-services and services resource respectively. All the CSR resources will be managed by GeoNetwork v2.6 which also provides CSW interface for search and harvest. GEOSS CSR Version 2.2: service interfaces can be registered independently
November 22, 2011 Components and services have been merged into resources in CSR 2.2 and service interfaces can be registered independently. In the current version, service interfaces are special resources since a service interface can be associated with a registered resource to provide detailed access information while all the other resource categories are general resources. GEOSS CSR Version 2.1: records have new URNs
November 22, 2011 Clearinghouses may take advantage of the new URNs to identify CSR records. GEOSS CSR Publication Portal secured
March 29, 2010 GEOSS Component and Service Registry Publication Portal now supports Hypertext Transfer Protocol Secure (HTTPS) protocol. When accessing to the 'Publication Portal', secured connection will be automatically enabled. GEOSS CSR Records Approval Process Enabled
May 25th, 2009 Each CSR record will be manually approved to make sure that it meets the quality assurance criteria. Only approved records are listed in the holding page, searchable through the public non-secure search interface, and viewable through the API interface. Components and/or Service providers may submit "request for approval" notice to the CSR Record Review Working Group in the registration portal, which will trigger a manual check process. GEOSS CSR Version 2: Interoperable System has been published
May 23, 2009 GEOSS Component and Service Registry Publication Portal now supports Hypertext Transfer Protocol Secure (HTTPS) protocol. When accessing to the 'Publication Portal', secured connection will be automatically enabled. GEOSS CSR Version 2: Interoperable System Testing and Maintenance Schedule
May 7, 2009 The Registration System will be down for Version 2: Interoperable System testing and maintenance on Thursday, May 7th, 2009 from 9:00 pm EDT (Friday, May 8, 2009 at 01:00 am UTC). During this time, all partners and clients will be unable to utilize Registration/Search/Modify functionalities. The Version 2 system will be interoperable with GEOSS Standards Registry System (SIR) and capable of retrieving registered Standards and Special Arrangements in SIR on the fly during Service Instance registration and modification in CSR. The Registration System will be available again at Friday, May 8th, 2009 from 10:00 am EDT (Friday, May 8, 2009 at 02:00 pm UTC). Thank you for your cooperation. Registration System Preventative Maintenance
April 28, 2009 The Registration System will be down for scheduled maintenance on Wednesday, April 29, 2009 from 9:00 am EDT (13:00 pm UTC). During this time, all partners and clients will be unable to utilize Registration/Search/Modify functionalities. A status message will be displayed here when the system is available. Thank you for your cooperation. API Interface Update Complete
April 8, 2009 The GEOSS CSR system is now available for all registration/search/modify/delete functionalities, with API interface enhanced. Clearinghouse providers are recommended to check out the API Interface page to see the updated request/response examples. Thank you for your cooperation. API Interface Update Notice
April 7, 2009 The GEOSS CSR will be down on April 8th, 2009 from 9:00am to 10:00am EDT for the release of new system update into operations. This update fixes some reported namespace issues. During this time, all partners and clients will be unable to utilize Registration/Search/Modify functionalities. Thank you for your cooperation. Registration System Available
December 8, 2008 The GEOSS CSR system is now available for all registration/search/modify/delete functionalities. Thank you for your cooperation. Registration Portal Preventative Maintenance
December 5, 2008 The Registration Portal will be down for scheduled maintenance on Sunday, December 7th, 2008 from 9:00 am EST (14:00 pm UTC) to 5:00 pm EST (22:00pm UTC). During this time, all partners and clients will be unable to utilize Registration/Search/Modify functionalities. A status message will be displayed here when the system is available. Thank you for your cooperation. CSW Interface Under Upgrade
September 19, 2008 The legacy CSW interface is under upgrade to support OGC Catalogue Service 2.0.2 baseline profile(core queryable/core returnable). Service Association On The way
September 19, 2008 Service providers will be able to define/modify/delete service association between any two of their service offerings in the GEOSS Publication portal. Ongoing Registries Integration
December 10, 2007 Integration between the Components and Services Registry and the Standards and Interoperability Registry is ongoing.
The intention of the synchronization work between these two registries is to synchronize content both ways: |
|