Bug #5254

pre-process date fields before indexing in elastic search

Added by Justin Simpson almost 9 years ago. Updated about 8 years ago.

Status:NewStart date:06/19/2013
Priority:MediumDue date:
Assignee:Mike Cantelon% Done:

0%

Category:Dashboard
Target version:-
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:

Description

In the metadata entry templates, in the dashboard, users can enter things like creation date. Archivematica 0.10 is indexing the contents of these field in ElasticSearch. Everything entered is getting put into a single field in an Elastic Search document, and Elastic Search is attempting to automagically determine the type of this field. Elastic Search therefore is expecting to see a single date object in that field.

Archivematica should probably pre-process the contents of that field, and detect when there is more than one date entered, and index it as a multi-valued field in ElasticSearch (i.e. submit more than one CreationDate field in the json document sent to ES).

A related issue is when the dates entered do not fit the expected format. For example, a user may enter 'August 2011' as a date, rather than '2011-08-01'. The dashboard should validate the contents of these form fields, either by enforcing a specific date format, or by changing the text entered to be in a valid date format that ES can handle.

History

#1 Updated by Courtney Mumma almost 9 years ago

  • Tracker changed from Feature to Bug
  • Assignee set to Mike Cantelon
  • Target version set to Release 1.0.0

#2 Updated by Courtney Mumma over 8 years ago

  • Target version changed from Release 1.0.0 to Release 1.1.0

#3 Updated by Justin Simpson about 8 years ago

  • Target version deleted (Release 1.1.0)

Also available in: Atom PDF