Project

General

Profile

Story #4278

EML indexing - handle multiple temporalCoverage and spatialCoverage elements

Added by Ben Leinfelder over 7 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_indexer
Target version:
Start date:
Due date:
% Done:

0%

Story Points:

Description

Our current index schema only supports single values for coverage elements. This is makes things simple (no confusing multiple non-contiguous coverage as continuous) but it discards a lot of potential information that would be useful for discovery.

We should be effectively indexing these coverage elements and all their values.

temporalCoverage (including multiple single date times):
beginDate
endDate

spatialCoverage:
eastBoundCoord
westBoundCoord
northBoundCoord
southBoundCoord

History

#1 Updated by Dave Vieglais over 6 years ago

  • Project changed from Infrastructure to CN Index

#2 Updated by Dave Vieglais over 4 years ago

  • Category set to d1_indexer
  • Target version set to CCI-2.4.0
  • Project changed from CN Index to Infrastructure
  • Milestone set to None

#3 Updated by Dave Vieglais over 3 years ago

  • Assignee set to Jing Tao

#4 Updated by Dave Vieglais over 3 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)