Ticket #1078 (closed task: fixed)

Opened 12 years ago

Last modified 12 years ago

Support for full-text search within specific MEDIN element #1

Reported by: mpritcha Owned by: sdonegan
Priority: critical Milestone: MEDIN
Component: discovery Version:
Keywords: discovery medin Cc:


Expecting list of specified elements from MEDIN metadata profile for which full-text search within that element should be supported. Likely to be 5-7 of these.

Should be a case of (in each case):

  • adding additional vector to discovery index (database)
  • modifying ingestion code to populate new vector
  • modifying search SQL to make use of new vector
  • modifying client search interface to execute modified search
    • (not specifically required by MEDIN but needed to test correct function)

Change History

comment:1 Changed 12 years ago by mpritcha

  • Type changed from defect to task

comment:2 Changed 12 years ago by mpritcha

  • Priority changed from blocker to critical

comment:3 Changed 12 years ago by sdonegan

  • Status changed from new to assigned

The additional list of specific MEDIN elements for new "TermTargets?" has been established with the ingest system pulling these out of the input xml, filling the relevant db column with the required element type and content. The API will now also allow the multiple selection of these TermTargets? (according to the TermTargetList?) and will allow searching within them. Many of the additional elements are also added within the "additionalInformation" elements in a documentBreif and documentFull information return in doSearchReturn and doPresentReturn as requested by the GeoData? developers.

comment:4 Changed 12 years ago by sdonegan

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.