VuFind
  1. VuFind
  2. VUFIND-480

Add dynamic fields to Solr schema for easier customization

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3
    • Component/s: Search
    • Labels:
      None

      Description

      We should add some dynamic fields (see http://wiki.apache.org/solr/SchemaXml#Dynamic_fields ) to make it easier for users to add custom fields to their VuFind indexes without being forced to modify the Solr schema.

      Before adding this feature, we need to decide on a naming convention -- should we use a prefix or suffix? How should we represent field types? What field types do we need to support? How do we indicate whether fields are stored and/or multivalued? Which combinations of these settings do we need/want to support?

      Please comment on this ticket if you have ideas or preferences.
      1. dynamicfields.patch
        2 kB
        Demian Katz
      2. localsearchspecs.patch
        1 kB
        Demian Katz

        Activity

        Hide
        Vaclav Rosecky added a comment -
        Add dynamic field for browse type to allow custom indexes for browsing ISBN, ISSN etc.

        <dynamicField name="*_browse" type="string" indexed="true" stored="false" multiValued="true"/>
        Show
        Vaclav Rosecky added a comment - Add dynamic field for browse type to allow custom indexes for browsing ISBN, ISSN etc. <dynamicField name="*_browse" type="string" indexed="true" stored="false" multiValued="true"/>
        Hide
        Demian Katz added a comment -
        I see how this would be useful, but I wonder if it would be better to come up with a naming convention for unstored versions of fields since this type of field might be useful for other purposes as well... though then we end up with a profusion of field definitions as opposed to just one.
        Show
        Demian Katz added a comment - I see how this would be useful, but I wonder if it would be better to come up with a naming convention for unstored versions of fields since this type of field might be useful for other purposes as well... though then we end up with a profusion of field definitions as opposed to just one.
        Hide
        Ronan McHugh (Inactive) added a comment -
        Hi, just wondering if there is any interest in adding this to the Authority Index at some point?
        Show
        Ronan McHugh (Inactive) added a comment - Hi, just wondering if there is any interest in adding this to the Authority Index at some point?
        Hide
        Demian Katz added a comment -
        As of r5908, I've added dynamic fields to the authority core for consistency with biblio. Since authority doesn't define as many field types, the list is shorter, but date, string and text are supported using the same suffixes as in biblio. This change will be available in releases 1.4 and 2.0alpha.
        Show
        Demian Katz added a comment - As of r5908, I've added dynamic fields to the authority core for consistency with biblio. Since authority doesn't define as many field types, the list is shorter, but date, string and text are supported using the same suffixes as in biblio. This change will be available in releases 1.4 and 2.0alpha.
        Hide
        Ronan McHugh (Inactive) added a comment -
        great, thanks!
        Show
        Ronan McHugh (Inactive) added a comment - great, thanks!

          People

          • Assignee:
            Demian Katz
            Reporter:
            Demian Katz
          • Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: