Search results

Jump to: navigation, search
  • ==== Project Links ==== [[NSDL Registry]] Project (Now named Open Metadata Registry)
    1 KB (198 words) - 12:44, 7 August 2014
  • === An NSDL Registry: Supporting Interoperable Metadata Distribution === ...In particular, we intend to seed development of the Registry with the DCMI Registry open source application. </i>
    2 KB (301 words) - 15:09, 1 February 2009
  • == Registry Project Task List (Draft) == ...sion and recruitment through the NSDL Communication Portal and through the NSDL Whiteboard Report immediately upon award.
    3 KB (496 words) - 12:51, 17 August 2005
  • ====Registry Use Cases==== Note that the NSDL Registry is now the Open Metadata Registry (the URL is the same: http://metadataregistry.org)
    3 KB (369 words) - 13:52, 9 September 2010
  • =NSDL REGISTRY USE CASES= ...ion wishes to publish this information to the wider community via the NSDL registry. To publish requires the following steps. The Element Set publisher:
    11 KB (1,744 words) - 13:50, 29 August 2005
  • ...ribed elsewhere. Functionality will be phased from Year 1 to Year 2 of the project, with some tasks done manually in the first year, eith additional automatio #*Basic explanatory text about the registry
    17 KB (2,340 words) - 08:01, 1 November 2006
  • #Update on installation of DCMI Registry software. ... that can be used to help us a) maintain interest and excitement about the project, and give us a public space to discuss registries in general and invite com
    3 KB (490 words) - 12:01, 24 August 2005
  • = [[NSDL Registry]] = # Install software, configure at Cornell for initial use by NSDL and GEM Exchange research and development site at the University of Washing
    3 KB (454 words) - 06:26, 29 August 2005
  • 3. Presentation on the Registry Project timeline and goals (Stuart?) * Alpha and Beta testing for Registry
    750 B (93 words) - 08:01, 20 October 2005
  • ...iki/index.php/NSDL_Registry_Use_Case_Documentation_%28Vocabularies%29 NSDL Registry Use Cases (Vocabularies)] ...l.washington.edu/wiki/index.php/NSDL_Registry_Functional_Requirements NSDL Registry Functional Requirements]
    3 KB (474 words) - 16:32, 16 October 2005
  • =Registry Use Cases (Vocabularies)= ;Purpose:An NSDL project has a small subject vocabulary that they wish to register and needs to regi
    15 KB (2,290 words) - 18:52, 27 March 2010
  • * Registry Managers #Use cases are focusing on project start, but we should attempt to flesh out where we want to go second year (
    2 KB (245 words) - 12:12, 5 October 2005
  • =Registry Use Case: Schemas= ...ization wishes to enter the description of a schema (element set) into the Registry. This step is necessary before identifying specific elements (properties) o
    19 KB (2,914 words) - 19:39, 27 March 2010
  • =Registry Use Cases: Application Profiles= ...ization wishes to enter the description of an application profile into the Registry. This step is necessary before identifying specific terms or uploading an e
    21 KB (3,143 words) - 19:46, 27 March 2010
  • Registry Manager ...s responsible for the administrative tasks involved in the management of a registry
    8 KB (1,141 words) - 18:49, 27 March 2010
  • Audience: New Registry Work List, NSDL_All ...Vocabulary Workshop. We believe strongly that this Registry will allow the NSDL to move forward into improved interoperability within (we hope) a relativel
    2 KB (267 words) - 07:59, 31 October 2005
  • #*What pieces of the overall project will be funded by whom #* Lessons learned from GEM, from NSDL, from UIUC, will be incorporated
    4 KB (621 words) - 09:49, 13 December 2005
  • ...s process and conclusions in determining the best options for building the Registry and MMS. ...ning behind this piece of the process based on what had been available for NSDL.
    1 KB (161 words) - 13:03, 18 January 2006
  • .... One of the requirements that emerged was very much like the current NSDL Registry integration requirement to merge the new system with a collection registrat The need to work in a more collaborative environment and to release the project for wide deployment as open source software makes continued use of a commer
    6 KB (1,065 words) - 18:04, 18 January 2006
  • == Registry Project Meeting, Seattle, 4/28/06== ...historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary? We're thinking that the use of skos:inS
    6 KB (931 words) - 08:17, 24 May 2006

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)