1 / 8

Global Node Design

Global Node Design. What can you expect. What do we expect. agreement agreement go ahead awareness direction. User Requirements Software Requirements Detailed Solution Impact Next steps. User Requirements. One Root Node (RN) per Retrieval Manager.

nansen
Download Presentation

Global Node Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global Node Design

  2. What can you expect What do we expect • agreement • agreement • go ahead • awareness • direction • User Requirements • Software Requirements • Detailed Solution • Impact • Next steps

  3. User Requirements One Root Node (RN) per Retrieval Manager • 1. A user should be able to obtain a list of all RNs • 2. A user should be able to obtain a theme description of all RNs • 3. A user should be able to obtain all local collections from every RN • 4. A user should be able to obtain all local collections from a selected RN

  4. Software Requirements • A Global Node (GN) is a theme collection • A GN is replicated (see also management) • A local GN search  RN_identifier  Theme Keyword • A local GN present  RN_identifier + Theme  ‘complete RN collection descriptor’ • A remote GN search  RN_identifier • A remote GN present  RN_identifier + Theme Collection_identifier + • Theme- + Spatial- + Temporal Keyword

  5. Software Requirements

  6. Detailed solution (data) • Global Node Collection • Collection Descriptor • ItemDescriptorID Theme Collection Item Descriptor ID • ItemDescriptorName Global Collection • CollectionType • CollectionHierarchyCategory ‘Global’ • IncludedCollectionDescriptors • ItemDescriptorID ThemeCollection Root RM1 • ItemDescriptorID ThemeCollection Root RM2 • ItemDescriptorID ThemeCollection Root RM3 • ItemDescriptorID ThemeCollection Root RM4 • ItemDescriptorID ThemeCollection Root Local • Where to store the ThemeKeyword’s for each ThemeCollection Root? • IncludedCollectionDescriptors = 1 { ItemDescriptorId++} n + • ItemDescriptorId++ = • ItemDescriptorId + • Theme Keyword

  7. Detailed solution (search) • Options for ‘otherinfo’ in the Search message • Local is the current default • Global Local which will only target the Global Node and included roots • Global Remote will target the Global Node and all included roots and their included collections (Local or remote) • Remote will target the root node of the local coll structure or a specified collection • within the local collection structure and any included collections local or remote. Current capability

  8. Impact and next steps • Explain • theme keyword • Search • force local search in other sites • Existing Collection Structures • change in structure (theme keyword) • Federation Management • introduction of replication • ... • Next steps

More Related