> > > >
The Search Framwork Configuration controls what is displayed on the Search Workbench and to a large degree how the Search Workbench operates.
Note
To see the system defaults for 1.5, see the Jira OLE-6360.
The Search Framework Configuration screen is divided into 5 parts with each part controlling a different aspect of the Search Workbench: Doc Types, Doc Formats, Doc Fields, Search Result Page Size, and Facet Page Size.
The Doc Types tab has 3 columns and as many rows as are needed to define the various doc types of records stored in DocStore. These Doc Types are what are displayed on the Search Workbench in the Document Type drop down:
They are also used in the other sections of the Search Framework Configuration as described below.
Multiple doc types can be added to the search framework configuration by filling in all of the required fields and clicking the add button.
Warning
DO NOT ADD OR CHANGE ANY VALUES IN THIS SECTION WITHOUT FIRST CONSULTING WITH A PROGRAMMER. Code changes are needed to support a new document type.
Doc Types Column definitions
Title |
Description |
Name |
Required. A unique name of the Doc Type. This will appear within the code. |
Label |
Required. A label for the Doc Type. This will appear in the Doc Type lookup on the Search Workbench. |
Description |
Optional. A description for the Doc Type. |
The Doc Formats tab allows you to define multiple formats for document types and to provide each with a distinct label. The values in the drop down “Document Type” are from the Doc Types definitions described above.
To work with the Doc Formats section, first select a Document Type in that drop down.
Selecting Document Type Bibliographic will display the 3 formats defined for 3 different Bibliographic formats: Dublin Core, Dublin Unqualified, and MARC.
Selecting Document Types EHolding, Holding and Item will display a single document format definition for each. For all of these document types, the format is oleml (OLE Markup Language – an xml format).
Selecting Document Type License displays 4 different formats for License. The definitions are DOC (Word Doc), ONIXPL (ONIX for Publications Licenses), PDF (Adobe), and XSLT (Extensible Stylesheet Language Transformations).
The format definitions along with the Doc Types are used in the Doc Fields section described below.
Multiple doc formats can be added to the search framework configuration by filling in all of the required fields and clicking the add button.
Warning
DO NOT ADD OR CHANGE ANY VALUES IN THIS SECTION WITHOUT FIRST CONSULTING WITH A PROGRAMMER. Code changes are needed to support a new document type.
Doc Format Column definitions
Title |
Description |
Name |
Required. A unique name of the Doc Format. This will appear within the code. |
Label |
Required. A label for the Doc Format. |
Description |
Optional. A description for the Doc Format. |
The Doc Fields tab controls the fields that are available for searching, the fields that are displayed in the results, the fields that can be globally edited in the Global Edit screen, and the fields that will be exported in an XML format from the search results. It also controls the definitions of those fields in terms of the values recorded in the bibliographic records. For example a field called Title can be defined in terms of MARC fields.
Note
Changes to some Doc Fields values will only affect records added or edited after the change is made because an indexing update is necessary to alter the display.
In order to index and reindex bibliographic, holdings, e-holdings, and item records in Solr, go to http://demo.docstore.ole.kuali.org/admin.jsp (or http://tst.docstore.ole.kuali.org/admin.jsp if you are in the tst environment).
Click the Start button.
Click Show Status button to see the status.
Indexing is complete when you see the "Index End Time"
To use this section, you need to select values from both the drop downs: Document Type and Document Format. The values for these lists are from the previous sections Doc Types and Doc Formats. Selecting a Doc Type will change the values in the Document Format section.
Depending on the Document Type selected from the drop down, different columns will be displayed.
Selecting Document Type Bibliographic and Document Format MARC displays columns:
Name, Label, Description, Path Include, Path Exclude, Is Search, Is Display, Global Edit, Is Export, and Is Facet.
A Note on Titles: What OLE displays as Title in the search results is Title_sort. If you modify Title_display you will not see the results. However if you mouse-hover over a Title_sort value in the Search Workbench, you will see the Title_display value.
Multiple doc fields can be added to the search framework configuration by filling in all of the required fields and clicking the add button.
Doc Fields definitions
Title |
Description |
Name |
Required. This is the name of the field used in Solr configuration. Please note that each Name value here must have the same name in the Solr configuration. WarningAdding a name here must be accompanied by a reconfiguration of Solr to be effective. Changing an existing Name value here without a corresponding name change in Solr will have unforeseen consequences . |
Label |
Required. This is what the users will see displayed as search values in the ‘In Field’ drop down on the Search Workbench for selecting the search criteria for Names ending in “_search” and the column names for search results for Names ending in “_display”. This can be changed without any corresponding change in Solr Configuration. NoteAs of this writing, changing the value for an existing Label does not affect what the users see. |
Description |
Optional. This is just for documentation. It does not have any impact on what the user sees on the Search Workbench. |
Path Include |
Optional. For Bibliographic Marc format fields, this is a reference to the underlying MARC fields and subfield codes. Entering a MARC field and subfield here defines what fields are displayed or searched on when this field is displayed in the search results or searched if selected in the search criteria. The default values displayed were derived from the OLE Search Technical Documentation page (section 1.3) on OLE’s Wiki page. There is a specific syntax to be used for both Path Include and Path Exclude. See Path Syntax below. |
Path Exclude |
Optional. For Bibliographic MARC format fields, this is a limitation on the Path Include values. If the path include for Title_display field for example was “245”, a value of “245-c” in this column would cause all values in 245 subfields to display except for the value in subfield 245 c. See Path Syntax below for a definition of the syntax to be used. |
Is Search |
Optional. Checking this box for a field will cause the field label to appear as a value in the “In Field” drop down on the Search Workbench. Removing the check will cause that field to disappear from those drop down values. Only check fields in this column which have “_search” as the last part of their names. See Cautionary Notes below. |
Is Display |
Optional. Checking this box for a field will cause the field label to appear as a column in the search results on the Search Workbench. Removing the check will cause that field column to disappear from the search results display on the Search Workbench. Only check fields in this column which have “_display” as the last part of their names. See Cautionary Notes below. |
Global Edit |
Optional. Checking this box for a field will allow the field to be edited in the Global Edit screens. A Global Edit screen for Bibliographic records is a future enhancement. This column will likely be hidden until that enhancement is ready. |
Is Export |
Optional. This is for a future feature that will allow export of fields in csv format. It has no impact on the “Export to Doc XML” function displayed under the search results on the Search WorkBench screen. |
Is Facet |
Optional. Checking this box will cause the Label for this field to appear in the “Narrow Search” section of the Search Workbench screen when searching for Bibliographic records. Only check fields in this column that have “_facet” as part of their names. See Cautionary Notes below. |
Actions |
Click add before clicking saveto add extra rows to the Doc Fields tab. |
There is a specific Path syntax to be used in the Path Include and Path Exclude column values for a field. Here are examples of the syntax.
245-a means MARC field 245, subfield a. This is the value that will be searched or displayed for that field name.
245-a;b means MARC field 245 subfield a and subfield b. The semi colon means that for display fields, the value displayed will be the concatenated values of those subfields.
234-c, 245-6 means MARC field 245 subfield c and field 245 subfield 6 will be displayed, the comma will cause those two values to display on two lines in the search results.
600,610,69* means all the subfields of 600 will be concatenated and displayed on the first line, all the subfields of 610 will be concatenated and displayed on the second line, all the values of all the subfields of all fields starting with 69 will be concatenated and displayed on a third line.
Note: There are some nonstandard subfields in a few of the default values that should not be confused as some kind of syntax. Examples include the Author_display Path Exclude field. The values “100-=” and “100-?” are actually subfields for the 100 field used by some of OLE’s partner institutions’ current systems – not syntax. It is likely that those subfields will not be used in OLE and will be removed from these default field definition values.
Selecting Document Type Holding, EHoldings, or Items and Document Format OLEML displays columns:
Name, Label, Description, Is Search, Is Display, Global Edit, Is Export, and Is Facet.
Multiple doc fields can be added to the search framework configuration by filling in all of the required fields and clicking the add button.
Doc Fields definitions
Title |
Description |
Name |
Required. This is the name of the field used in Solr configuration. Please note that each Name value here must have the same name in the Solr configuration. WarningAdding a name here must be accompanied by a reconfiguration of Solr to be effective. Changing an existing Name value here without a corresponding name change in Solr will have unforeseen consequences . |
Label |
Required. This is what the users will see displayed as search values in the ‘In Field’ drop down on the Search Workbench for selecting the search criteria for Names ending in “_search” and the column names for search results for Names ending in “_display”. This can be changed without any corresponding change in Solr Configuration. NoteAs of this writing, changing the value for an existing Label does not affect what the users see. |
Description |
Optional. This is just for documentation. It does not have any impact on what the user sees on the Search Workbench. |
Is Search |
Optional. Checking this box for a field will cause the field label to appear as a value in the “In Field” drop down on the Search Workbench. Removing the check will cause that field to disappear from those drop down values. Only check fields in this column which have “_search” as the last part of their names. See Cautionary Notes below. |
Is Display |
Optional. Checking this box for a field will cause the field label to appear as a column in the search results on the Search Workbench. Removing the check will cause that field column to disappear from the search results display on the Search Workbench. Only check fields in this column which have “_display” as the last part of their names. See Cautionary Notes below. |
Global Edit |
Optional. Checking this box for a field will allow the field to be edited in the Global Edit screens. A Global Edit screen for Bibliographic records is a future enhancement. This column will likely be hidden until that enhancement is ready. |
Is Export |
Optional. This is for a future feature that will allow export of fields in csv format. It has no impact on the “Export to Doc XML” function displayed under the search results on the Search WorkBench screen. |
Is Facet |
Optional. Checking this box will cause the Label for this field to appear in the “Narrow Search” section of the Search Workbench screen when searching for Bibliographic records. Only check fields in this column that have “_facet” as part of their names. See Cautionary Notes below. |
Actions |
Click add before clicking saveto add extra rows to the Doc Fields tab. |
Notes about some of the Field Name rows defined for Holdings, Items and Eholdings:
Title_display is needed.
Some current fields like Title_Facet, Title_search, Title_sort are not meaningful here and will be removed.
Fields like “CallNumber_display” and “CallNumber_search” can be merged into a single field. We anticipate that this will be done soon.
The question has come up about the significance of the “_display”, “_search”, “_facet”, “_sort” that are included in the Name column. If all of those different names for the same type of field are defined exactly the same in the Path Include and Path Exclude fields, can one of those fields have the Is Search, Is Display, Global Edit, and Is Facet boxes checked and the other fields ignored. This is something that still needs to be tested. Until then, only check the boxes as described above.
The field Names ending in “_sort” are for internal use and exist primarily for the possible suppression of initial characters in the subfield value. We are not yet sure if there is a use case for having different values in the Path Include and Path Exclude fields for this Name than are present for the same field with “_display” at the end. At present the Path Include and Exclude values for Names ending with “_sort” are the same as those ending with “_display”.
If a change is made in the Path Include or Path Exclude for any of the existing Names, the change will only be effective for bibliographic records created after the change. A re-index of the bibliographic records will be required to make that change effective for records that existed before the change. Even if the Name is a “_display” field, it will require a re-index to be effective for existing documents.
Note
In order to index and reindex bibliographic, holdings, e-holdings, and item records in Solr, go to http://demo.docstore.ole.kuali.org/admin.jsp (or http://tst.docstore.ole.kuali.org/admin.jsp if you are in the tst environment).
Click the Start button.
Click Show Status button to see the status.
Indexing is complete when you see the "Index End Time"
Note: There are some nonstandard subfields in a few of the default values that should not be confused as some kind of syntax. Examples include the Author_display Path Exclude field. The values “100-=” and “100-?” are actually subfields for the 100 field used by some of OLE’s partner institutions’ current systems – not syntax. It is likely that those subfields will not be used in OLE and will be removed from these default field definition values.
Multiple Search Result Page Sizes can be added to the search framework configuration by filling in all of the required fields and clicking the add button.
Search Result Page Size Column definitions
Title |
Description |
Size |
Required. The number of search results displayed options available with each search's Result's Show __ Entries . |
Modify tabs within the Search Framework Configuration page. Consult a programmer before adding or modifying some of the sections, these are noted above.
Click to save any changes or additions you have made. You must save each section that you modify.
Click to discard any changes you have made since the section was last saved. The reset function only restores everything from the database, by clicking the button any changes made in the session without clicking save will be reverted.
An example of how indexing and searching is done:
When a Bib MARC record is added or updated, the following fields are generated for this record and indexed in Solr:
Title_search - This is a multi-valued field and the values are generated by taking all the subfields of the datafields 245,130,240,246,247,440,490,730,740,773,774,780,785,830,840 (Path Include values) and excluding the subfields
245-c,245-6,245-c,245-6,130-c,130-6,240-c,240-6,246-c,246-6,247-c,247-6,440-c,440-6,490-c,490-6,730-c,730-6,740-c,740-6,773-c,773-6,774-c,774-6,780-c,780-6,785-c,785-6,830-c,830-6,840-c,840-6 (Path Exclude values)
So there can be 15 values of Title_search generated, assuming all of the above data fields have values.
Title_display - 245-a;b - This is a single-valued field and its value is generated by concatenating subfields a and b of datafield 245
When a search request (Title = ‘ole’) is submitted, the query is built and sent to solr. The value ‘ole’ is looked for in the 15 or so values of Title_search field of every bib record in Solr. If found, the single value of Title_display of the matched record is returned from Solr as a search result row.
(So, the value searched for may not appear in the displayed search result row.)
Both _search and _display fields are updated in Solr whenever a MARC record is added or updated in OLE. And the Path Include and Path Exclude definitions that are available at that time will be used for updating Solr.
So if the Path Include and Path Exclude are modified for either the _search or _display field, these modifications will not affect the records already indexed in Solr, until they are reindexed.
Is_search property of Title_search field tells whether the user can run a search against this field.
Is_display property of Title_display field tells whether the user can see this column in search result grid.