eXtensibleCatalog / Drupal-Toolkit

The eXtensible Catalog Drupal Toolkit
0 stars 0 forks source link

Index options in Solr - index as field #313

Open patrickzurek opened 7 years ago

patrickzurek commented 7 years ago

JIRA issue created by: rcook Originally opened: 2011-06-21 01:48 PM

Issue body: (nt)

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-06-21 01:50 PM

Comment body:

Below from email. I am not sure if these is all set or not. Dave, can you either add some clarity and set some next step items for this, or if everything is set, please close.

-----Original Message----- From: Bowen, Jennifer Sent: Thursday, December 02, 2010 10:05 AM To: Kiraly, Peter Cc: Lindahl, David; Cook, Randall Subject: Question re how indexes are stored in Drupal Solr

Peter, I'm still trying to understand the implications of the various ways of indexing in Drupal Solr. Here is the way I'm thinking about this, and I hope you can map this to the categories that you've defined in your email below.

First of all, I'm assuming that all metadata in a record is searchable and retrievable as part of a "blob" using the generic search box - in Voyager we refer to this as "keyword anywhere". In ADDITION to that, we have the following other needs:

  1. The field is used as a component of a facet = your category 2, below
  2. The field can be hotlinked within a record display and a user can click on it to initiate another search for that particular value in that particular data element (e.g. click on "cats" as a subject in a record to find other items with subject "cats"). I know that we've somehow tied this ability to the facets - is this also category 2 below?
  3. A library can offer an "advanced" search capability for a particular field or group of fields, e.g. a search just for titles, rather than using the generic search box (we haven't implemented this yet) - how does this fit with the categories below? Is this what requires indexing "as a field"?
  4. A library can create a "browse" page for a particular data element, such as we've done on Find Videos and DVDs with directors. From your message below, I assume that this requires both "as fields" and "as part of one or more facets" since the only data element in that category is rdarole:director. Or is this just in both categories because we also want to enable this as part of a facet?

I guess what I really don't know is exactly what indexing an element "as a field" enables a library to do with it?

Jennifer

-----Original Message----- From: Péter Király [mailto:kirunews@gmail.com] Sent: Tuesday, November 09, 2010 10:58 AM To: Cook, Randall Cc: Lindahl, David; Bowen, Jennifer; Anderson, Benjamin D Subject: Re: incorrect fields stored in Drupal Solr

Hi,

Currently the following fields are indexed:

as fields: 'dcterms:title', 'dcterms:identifier', 'xc:type007', 'rdvocab:modeOfIssuance',

as part of one or more facets: 'xc:subject', 'xc:creator', 'dcterms:creator', 'xc:contributor', 'dcterms:contributor', 'rdarole:author', 'rdarole:compiler', 'rdarole:composer', 'rdarole:editor', 'rdarole:illustrator', 'rdarole:performer', 'rdarole:producer', 'rdarole:speaker', 'rdarole:translator', 'dcterms:language', 'xc:ISO639-3LanguageName', 'dcterms:issued', 'dcterms:date', 'dcterms:subject', 'dcterms:coverage', 'dcterms:spatial', 'xc:coverage', 'xc:spatial', 'xc:type', 'dcterms:type'.

as both: 'rdarole:director'

Péter