The fields of the Link Resolver Usage subject area can be used to create reports that provide both specific details of link resolver usage as well as a broad perspective of how the Alma link resolver is used. This provides libraries with a useful means of determining proper electronic collection development.
This subject area supplements the Usage Data subject area, which includes data from vendors, while the Link Resolver Usage subject area takes data directly from the Alma link resolver.
Using the Link Resolver Usage area, the Design Analytics you can create reports/dashboards for the Link Resolver Usage area and are able to answer the following types of business questions:
- How many times did users click View It in all sources over a specified period of time?
- How many times did users click View It in a specific source?
- How many times did users click View It and no results were produced?
- How many times did users click View It for a particular source that resulted in no full text?
- How many times did users click View It for the most frequently requested full?text journals from a particular source?
Star Diagram – Link Resolver Usage
The following lists the fields available in Link Resolver Usage.
Link Resolver Usage – Field Descriptions
OpenURL Context Measures
The OpenURL Context Measures table is a fact table that stores all measures relating to the OpenURL Context. All fields are taken from the CONTEXT_OBJECT table. The primary key is CONTEXT_OBJECT_ID.
|Number of Requests||The number of times an OpenURL request was sent to the Alma Link resolver.|
|Number of Clicked Requests||Indicates if at least one of the services was clicked||Values are 1 and 0. Each time a request is clicked, 1 is added to the total sum.|
|Number of Requests Without Services||The number of incoming OpenURLs that do not result in any services|
|Number of Services (total)||The total number of services offered per incoming OpenURL request|
|Number of Electronic Services||The number of electronic services that appear when a user clicks View it|
|Number of Digital Services||The number of digital representations that appear when a user clicks View it||In order for this field to have data, you must select the Include Representation services in link resolver statistics check box (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings).|
|Number of Clicked Services (total)||The total number of services clicked|
|Number of Electronic Clicked Services||The number of electronic services a user clicks from the View it menu|
|Number of Digital Clicked Services||The number of digital representations a user clicks from the View it menu.||In order for this field to have data, you must select the Include Representation services in link resolver statistics check box (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings).|
|% Clicks from Requests||The percentage of incoming OpenURL requests that were clicked||% Clicks from Requests = (Number of clicked requests / Number of Requests) * 100|
|% Requests Without Services from Requests||The percentage of incoming OpenURL requests that do not have services||% Requests Without Services from Requests = (Number of requests without services / Number of requests) * 100|
OpenURL Context Details
The OpenURL Context details table is a dimension table that stores the details of the OpenURL context object. The primary key is CONTEXT_OBJECT_ID. The context object is the part of the OpenURL that contains the metadata information that identifies the resource to which the OpenURL links.
|Title||The title of the OpenURL Context|
|Author||The Author of the OpenURL Context|
|ISSN||The ISSN of the OpenURL Context|
|ISBN||The ISBN of the OpenURL Context|
|Material Type||The Material Type of the OpenURL Context|
Network Inventory Group
|The network inventory group||This field allows you to filter and display link resolver usage by library or campus. This is relevant for institutions using the inventory network groups.|
|Request ID||The Request ID of the OpenURL Context|
|Article Title||The Article Title of the OpenURL Context|
|EISSN||The EISSN of the OpenURL Context|
|Source||The Source of the OpenURL Context||The database/index that generates an OpenURL to the link resolver in order to obtain context-sensitive services for an electronic resource citation/reference.|
|Source Type||The Source Type||
This field allows libraries to easily gather data about from where users are coming when using the Alma Link Resolver.
The following are the possible values for the Source Type field:
The Source Field
The Source field indicates is the database/index that generates an OpenURL to the link resolver in order to obtain context-sensitive services for an electronic resource citation/reference. It appears in the OpenURL after the dash—for example, after &rfr_id=info:sid/primo.exlibrisgroup.com-. It also appears in the Primo PNX record.
By comparing the Source with other parameters such as Number of Clicked Requests, you can analyze trends in the use of electronic resources.
The following are some guidelines that indicate how the source is determined:
- If a patron clicks on a title in Primo that is in Alma, the source is the source ID of the system.
- If the source has a colon in it, either the user was a staff member testing the link within Alma, or the user received access to an article from within a database by being referred back to the uresolver to see if the user has a subscription that covers it.
- If the source has an underscore or consists of letters such as wj (Wiley journals), the user received access to the article from a PCI record in Primo.
The source google does not have a colon and means Google Scholar.
The following is an example of an OpenURL with the source and other fields of the OpenURL Context Details table in bold:
The Request Date table is a dimension table that stores the details about the date of the request. The primary key of the table is DATE_KEY.
|Request Date||The date of the request.|
|Request Month Key||The month key of the request (for example: 1, 2, 3).||This field is recommended if you want to sort by month.|
|Request Month||The month of the request.||For example: January, February).|
|Request Full Month||The month and the year of the request.||For example: January 2014.|
|Request Quarter||The quarter of the request.||For example: Q1, Q2.|
|Request Year||The year of the request.||For example: 2014.|
|Request Fiscal Year||The fiscal year of the request.|
|Request Date Filter||Used to filter report results by date.|
|Request Date||Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific request date.||Using this column, a user may view the accumulative measures in each level of the hierarchy.|
The Bibliographic Details table is a dimension table that stores the bibliographic details of the physical item. The primary key of the table is MMS_ID.
The field descriptions can be found in the Bibliographic Details shared dimension.
|Field||Source in Alma (for Internal Reference)||Mapping from MARC|
|Title||Taken from display.title in the display section of the operational record||MARC 245 subfields a,b|
|Author||Taken from display.author in the display section of the operational record||List values, delimiter is (;)
|ISBN||Taken from search.isbn in the search section of the operational record||List values, delimiter is ;
MARC 020 a,e,z
|ISSN||Taken from search.issn in the search section of the operational record||List values, delimiter is ;
MARC 022 a,y,e,z
|Publisher||Taken from display.publisher_const_b in the display section of the operational record||MARC 260 b
MARC 264 b
Remove special characters and replace spaces.
|Publication Date||Taken from display.date_of_publication in the display section of the operational record||MARC 260 c|
|Publication Place||Taken from display.place_of_pu blication in the display section of the operational record||MARC 260 a|
|Place Code||Taken from display.place_code in the display section of the operational record||For MARC21 this is taken from 008 pos. 15-17|
|Material Type||Taken from search. material_type in the search section of the operational record||MARC control LDR Material Type|
|Begin Publication Date||Taken from display.begin_pub_date in the search section of the operation||For MARC21 this is taken from 008 pos. 7-10|
|End Publication Date||Taken from display.end_pub_date in the search section of the operation||For MARC21 this is taken from 008 pos. 11-14|
|Category of Material||Taken from display. category_of_material in the display section of the operational record||Position 0 of the 007 field of the bibliographic record|
|Bibliographic Level||Taken from display.bib_level in the display section of the operational record||Position 7 of the LDR field of the bibliographic record|
|Bibliographic ID||Taken from display.bib_id in the display section in the operational record||MARC 010 excluding numeric subfields|
|Network Number||Taken from search. other_system_number in the search section of the operational record||This field is called "other system number" in Alma List values. The delimiter is ;
MARC 035 or 019 excluding numeric subfields
|Edition||Taken from display.complete_edition in the display section of the operational record||MARC 250 subfields a,b|
|Language Code||Taken from display.language in the display section in the operational record||For MARC21 this is taken from 008 pos. 35-37|
|Series||Taken from display.series_small in the display section in the operational record||List values, delimiter is ;
|Subjects||Taken from display.subjects in the display section of the operational record||List values, delimiter is ;
MARC 6XX excluding numeric
|Type of Date||Taken from display. type_of_date in the search section of the operational record||For MARC21 this is taken from 008 pos. 6|
|Uniform Title||Taken from display.uniform_title in the display section of the operational record||MARC 240 excluding numeric subfields
MARC 130 subfields a,p
|Resource Type||Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see Working with the Resource Type Field.|
The following table describes other fields in the shared dimension (taken from Alma and not MARC):
|Field||Source in Alma (for Internal Reference)|
|Active Course Code||The code of an active course.|
|Active Course Name||The name of an active course.|
|MMS ID||Stores the MMS ID of the item|
|LC Classification Top Line||Stores the combined LC code and classification numbers until the first period followed by a letter such as NB933 when the lc_class_number is NB933.F44|
|Dewey Classification||Stores the Dewey Classification|
|Dewey Classification Top Line||Stores the first 3 digits of the Dewey Classification|
|Local Param1||This field allows you to enrich the bibliographic information exported to Analytics with additional information stored in MARC 9XX local fields in Alma.
In order to make use of this field, you must contact Ex Libris Support and supply them with a three-digit MARC field code (for example, 901). Following configuration of this field by Ex Libris Support, its value will be available in analytics.
|Local Param2||See the description above.|
|Local Param3||See the description above.|
|Local Param4||See the description above|
|Local Param5||See the description above|
|Creator||Stores the name of the user that created the record|
|Creation Date||Stores the creation date|
|Modified By||Stores the user name that modified the record|
|Modification Date||Stores the modification date|
|Suppressed from Discovery||Indicates whether the record is suppressed from external discovery systems|
|Bibliographic Lifecycle||The Lifecycle of the item. Possible values are Deleted and In Repository. This allows you to filter reports by In Repository/Deleted items.|
|Network ID||This field is used by institutions implementing a Network Zone. It is the same as the MMS ID of the bibliographic record in the Network Zone and can be used to create reports that show the MMS ID in the member institution (using the existing MMS ID), as well as the corresponding MMS ID in the Network Zone.|
|Title (Normalized)||The normalized Title. This field is useful when you want to use the normalized title from one subject area to compare with a report with fields from a different subject area.|
|ISSN (Normalized)||The normalized ISSN. This field is useful when you want to use the normalized ISBN from one subject area to compare with a report with fields from a different subject area. This field is built in the same manner in which the normalized title in Alma is built:
Alma does the following to the 245 field (except subfields c,h,6 and 8):
|The ISBN. Created for uniformity with Title (Normalized) and ISSN (Normalized).|
|Brief Level||The level of the brief record|
|Originating System||The system where the bibliographic record originated|
|Originating System ID||The ID of the system where the bibliographic record originated|
|Originating System Version||The version of the originating system|
Using this dimension, the user may drill down from Group1 to Group4. In each level, the user may see measures accumulated to the relevant group and see the number of items grouped by classification.
The field descriptions can be found in the LC Classifications shared dimension.
|Start Range||Stores the start range of the group such as PS501|
|End Range||Stores the end range of the group such as PS689|
|Classification Code||Stores the letters in the beginning of the range such as PS|
|Start Range Number||Stores the numbers that come after the letter in the start range|
|End Range Number||Stores the numbers that come after the letter in the end range|
|Group1||Stores the name of the first level|
|Group2||Stores the name of the second level|
|Group3||Stores the name of the third level|
|Group4||Stores the name of the fourth level|
New for December!
|Stores the name of the fifth level|
|Classifications||Stores the Hierarchy column that allows the user to drill down from the first level of the classification to the fourth level. Using this column provides the user with the option to view the accumulative measures. Note that the fifth level is not included in this field.|
Books can be classified with Dewey Classifications.
In Dewey Classifications, topics are ordered in a hierarchy that is indicated by a three digit number. The highest level of the hierarchy is indicated by a number with one significant digit followed by two zeros, such as 600. The second level in the hierarchy is indicated by a number with two significant digits followed by one zero, such as 630. The third level in the hierarchy is indicated by a number with three significant digits such as 636.
The field descriptions can be found in the Dewey Classifications shared dimension.
|Dewey Number||Holds the first 3 digits of the Dewey Classification.|
|Group1||Stores the name of the first level.|
|Group2||Stores the name of the second level.|
|Group3||Stores the name of the third level.|
|Dewey Classifications||Stores the Hierarchy column that allows the user to drill down from the first level of the Dewey Classification to the third level. Using this column provides the user with the option to view the accumulative measures (loans or returns) in each level of the hierarchy.|
The shared Institution dimension allows the network institution to view reports according to institution. It is available in every subject area. It contains the following fields:
|Institution Code||The code of the institution.|
|Institution Name||The name of the institution.|
If an analytics report is run from a member institution in a collaborative network implementing a Network Zone, all member institutions are included in the report for Institution Code and Institution Name.
If an analytics report is run from an institution that is not part of a collaborative network implementing a Network Zone, only the single institution from which the report is run is included in the report for Institution Code and Institution Name.
Reports involving data across a collaborative network implementing a Network Zone may take longer to run than reports within one institution.
Shared Dimensions with Other Subject Areas
For information concerning shared dimensions with other subject areas, see Shared Dimensions.