Industry standards and recommended practices have done much to streamline efficiency for all stakeholders in the e-resource life cycle. For instance, MARC is a universal standard for bibliographic records which can be ingested by most library systems. KBART is a format for transmitting package information and target URLs for link resolvers and OpenURL functionality. COUNTER helps libraries keep track of usage statistics in a standardized way, across content providers. Organizations like NISO have also helped steward new standards and best practices to help address specific pain points in the e-resource librarianship. Come hear from the Standards Committee member experts about a few of these standards, where they sit in the e-resource cycle, why they are so important, and the potential consequences of when proprietary practices prevail. Specific standards covered in this session will include KBART, EDI (Electronic Data Interchange), and COUNTER, from the library and publisher perspectives.

1. NASIG 37th ANNUAL CONFERENCE
Baltimore, MD | June 5-8, 2022
#NASIG2022
Code of Conduct: https://nasig.org/Code-of-Conduct

2. Many thanks to our sponsors for making the NASIG 37th Annual
Conference possible!

3. Common Ground:
June 7, 2022 2:30-3:30 PM EST
Ilda Cardenas, California State University - Fullerton
Beverly Geckle, Middle Tennessee State University
Matthew Ragucci, Wiley
The Importance of
Standards and
Recommended
Practices

4. Agenda
• Introduction & Background
• Electronic Data Interchange (EDI)
• Knowledgebase and Related Tools (KBART)
• Counting Online Usage of Networked Electronic Resources (COUNTER)
• Closing
• Questions
4

5. Introductions &
Background
Ilda Cardenas
Electronic Resources Librarian
California State University - Fullerton
5

6. What are standards?
The Merriam Webster dictionary defines a standard as:
“Something established by authority, custom, or general
consent as a model or example.”
https://www.niso.org/welcome-to-niso
6

7. Why are standards important?
• According to NISO, “Information standards increase efficiency, reduce errors, and
improve the user experience — making it easy for customers to find a book online,
ensuring your website is fully accessible, being able to trust your usage data, and much,
much more.”
–National Information Standards Organization (NISO) (https://www.niso.org/welcome-to-niso)
• The purpose of standardization in the management of e-resources is to support better
communication and interoperability across disparate systems in order to facilitate the
work of all parties involved, including librarians, publishers, and vendors. Mutually agreed-
upon standardized practices are created through consensus of a community that includes
all the stakeholders, leading to a broader acceptance.
- Betty Landesman (2016) Taming the E-Chaos Through Standards and Best Practices: An Update on Recent
Developments, Serials Review, 42:3, 210-215, DOI: 10.1080/00987913.2016.1211443
7

8. Challenges for implementing standards in the E-resource
lifecycle?
8
https://www.nasig.org/Competencies-Eresources
“Given the challenges for ERM
system, not a single
commercial, in-house or
open-source solution is
currently available that can
meet all the requirements in
managing the nitty-gritty of
e-resources on a regular
basis.”
Pradhan, S. (2013). Developing standards for
electronic resource management. International
Journal of Information Dissemination and
Technology, 3(4), 236-238.

9. Acquire – EDI
Beverly Geckle
Continuing Resources Librarian
Middle Tennessee State University
9

10. E-resource lifecycle - Acquire
10
https://www.nasig.org/Competencies-Eresources

11. EDI
11
What
Where
Who
When
Why
How
EDI

12. EDI
12
Who uses EDI?
 Business
 Government
 Healthcare
 Banking
 Publishing
 Library Sector
What
Where
Who
When
Why
How
Acquisitions/Serials
Subscription Agents / Book Vendors
Library system providers

13. EDI
13
 EDI = Electronic Data Interchange
 Technology
 Structured data
 Standard formats
What
Where
Who
When
Why
How

14. EDI
14
What
Where
Who
When
Why
How
STANDARD
FORMAT
VARIABLE
DATA
EDI
FILE

15. EDI
15
What
Where
Who
When
Why
How
Business Transactions

16. EDI
16
What
Where
Who
When
Why
How
$$$
Standards monthly
Business Transactions - Libraries

17. EDI
17
 Manual Process - inefficient
 Automated Process – efficient
What
Where
Who
When
Why
How
Business Transactions - Efficiencies

18. EDI
18
EDI Data Transfer – simplified
What
Where
Who
When
Why
How
Server A Server B

19. EDI
19
What
Where
Who
When
Why
How
Publisher’s Weekly 1990 & 1994

20. EDI
20
What
Where
Who
When
Why
How
1994-2003

21. EDI
21
What
Where
Who
When
Why
How
EDI format standards
X12
United States
ANSI (American National Standards)
1979

22. EDI
22
EDI format standards
EDIFACT
Electronic Data Interchange For Administration, Commerce and Transport
International
UNECE (United Nations Economic Commission for Europe)
1987
ISO 9735 (International Standards Organization)
What
Where
Who
When
Why
How

23. EDI
23
What
Where
Who
When
Why
How
EDItEUR
EDItEUR is the international group coordinating development of the
standards infrastructure for electronic commerce in the book, e-book
and serials sectors.
…leader in developing, supporting and promoting global standards
for the exchange of bibliographic information and of e-commerce
messages in the book and journal supply chains
https://www.editeur.org/2/About/#Intro
EDItEUR has adopted the EANCOM subset of EDIFACT

24. EDI
24
What
Where
Who
When
Why
How
EDIFACT Messages
 Message Types/Codes
 Segments
 Syntax
ORDERS (Purchase order)
INVOIC (Invoice)
OSTENQ (order status inquiry-claim)
Codes
Data
Punctuation etc

25. EDI
25
What
Where
Who
When
Why
How
EDIFACT format - EDItEUR

26. EDI
26
What
Where
Who
When
Why
How
EDIFACT Message Segments
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'
INVOIC:D:96A:UN:EAN008’

27. EDI
27
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
BGM+380:::JINV+0755928+43'
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

28. EDI
28
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
LIN+1'
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

29. EDI
29
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
LIN+2'
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

30. EDI
30
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
IMD+L+050+:::STANDARDS MONTHLY
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

31. EDI
31
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
MOA+203:2591’
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

32. EDI
32
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
RFF+LI:o10682661-1
Common
Match point
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

33. EDI
33
What
Where
Who
When
Why
How
EDIFACT Invoice Message Example
RFF+SNA:O0255130'
Common
Match point
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

34. EDI
34
What
Where
Who
When
Why
How
Invoice Example
2591.00
O0255130

35. EDI
35
What
Where
Who
When
Why
How
EDIFACT Message Segments
UNA:+.? '
UNB+UNOC:3+EBSCO:92+FOL0002:91+220218:0611+
17325'
UNH+17325-1+INVOIC:D:96A:UN:EAN008'
BGM+380:::JINV+0755928+43'
DTM+137:20220218:102'
NAD+BY+BR6569568::91'
NAD+SR+EBSCO::92'
CUX+2:USD:4'
LIN+1'
PIA+5+875357635:SA'
PIA+5S+0000-0000(20220101);1-F:SI::28'
PIA+5E+0000-0000(20221231);1-F:SI::28'
IMD+L+050+:::STANDARDS MONTHLY
QTY+47:1'
DTM+194:20220101:102'
DTM+206:20221231:102'
MOA+203:2591'
PRI+AAB:2591'
RFF+LI:o10682661-1'
RFF+SNA:O0255130’
LIN+2'

36. EDI
36
What
Where
Who
When
Why
How
Invoice Line in Library’s System
STANDARDS MONTHLY

37. EDI
37
What
Where
Who
When
Why
How
EDI configuration
Library System Field EDIFACT Segment Code
BGM+380+[1]
PO line number
MOA+203[2]
Vendor invoice number
RFF+LI[2]
Sub-total

38. EDI
38
What
Where
Who
When
Why
How
EDI configuration

39. EDI
39
What
Where
Who
When
Why
How
EDI Invoice Process

40. EDI
40
What
Where
Who
When
Why
How
EDIFACT: an oldie but a goodie!

41. KBART
Matthew Ragucci
Associate Director of B2B Product Marketing
Wiley
41

42. E-resource lifecycle
42
https://www.nasig.org/Competencies-Eresources

43. Definitions: Providers & Vendors
43
Content Provider
A content provider (or provider) is an organization that
provides access to online content through a license or for free.
Vendor
A vendor is an organization that creates library systems
products and services (using knowledgebases)
•Wiley
•SpringerNature
•Elsevier
•T&F
•Sage
Publisher
Library or
Consortium
Open
Access
Portal
Aggregator
DOAJ
DOAB
ROAR
OpenDOAR
EBSCO
ProQuest
Gale
Archives
Institutional
Repository

44. Definitions: Knowledgebases
44
• Databases vendors use to align
content provider products through
collections
• Required for vendor products
alignment
• Vendor feed from content providers
• Provider collections map to content
packages (not specific subscriptions)
• Collections can be created to reflect
institution-specific holdings
Local Knowledgebase
A database that shows the
resources a library is entitled
access to electronically or also in
print. Also known as “holdings.”
Global Knowledgebase
A database made up of collections
that are available to libraries to build
and align local knowledgebases. Also
known as “vendor KBs.”

45. Definitions: KBART
• KnowledgeBase And Related Tools
• Recommended practice created in 2007 to
ensure the timely transfer of accurate data to
knowledgebases vendors and link resolver
providers
• Data sources for knowledgebases
• Created by content providers & libraries
• Has evolved overtime to meet emerging
needs of libraries (books, OA, consortia)
• Files subject to updates (data corrections, link
updates, new publications,
transfer/withdrawn titles)
45
1. publication title
2. print identifier
3. online identifier
4. date first issue online
5. number first vol online
6. number first issue online
7. date last issue online
8. number last vol online
9. number last issue online
10. title url
11. first author
12. title id
13. embargo info
14. coverage depth
15. notes
16. publisher name
17. publication type
18. date monograph
published print
19. date monograph
published online
20. monograph volume
21. monograph edition
22. first editor
23. parent publication title id
24. preceding publication
title id
25. access type
KBART Phase II Data Fields

46. KBART file for serials content
46
publication_title print_id
entifier
online_ide
ntifier
date_first_issue_
online
num_first_vol_
online
num_first_issue
_online
date_last_issue
_online
num_last_vol_
online
num_last_is
sue_online
title_url first_author
Standards
Monthly
001-
8765
0002-5432 1997 33 1 https://standardsjournals.com/loi/
00025432
Journal of the
Data Standards
Society
0001-
9876
0002-4321 1964 1 1 1996 32 12 https://standardsjournals.com/loi/
00024321
title_id embargo
_info
covera
ge_dep
th
not
es
publisher_
name
publication
_type
date_monograph
_published_print
date_monograph_
published_online
monograph
_volume
monograph_
edition
first_
editor
parent_publicati
on_title_id
preceding_public
ation_title_id
access
_type
10.1111/(ISSN)
0002-5432
fulltext Data
Standards
Society
Serial 0002-4321 P
10.1111/(ISSN)
0002-4321
fulltext Data
Standards
Society
Serial P

47. KBART in practice
47
From “KBART: Knowledge Bases and Related Tools” (p. 6), by
NISO/UKSG KBART Working Group. 2010 (link).
Copyright 2010 by the National Information Standards
Organization and the UKSG.
1
2
3
4

48. KBART: A Brief History
48
2011
KBART provider
endorsements
2010
Phase I
Recommended
Practice released
2007
UKSG/NISO working
group starts
2019
KBART Automation
Recommended
Practice released
2017
KBART Automation
Working Group
formed
2014
Phase II
Recommended
Practice released /
NISO Standing
Committee

49. Knowledgebase benefits & impact
49
• They are the only true path to version of record
• Essential to OpenURL linking products
• Authority on content targets (they know where it is)
• Assist in the identification of institution-level access
• Help with the integration of discovery and ERM tools
• Non-existent or incorrect data make this impossible
OpenURL and
Link resolvers
MARC Records
Discovery Layers
Usage Statistics
A-Z Journal Lists

50. How KBART files work for libraries
50
• Alignment - find or create a stock product
KB collection that matches purchase
• If a package matches a “frontlist” or
“subject” collection, very easy to find and
use – these products also sold to other
libraries
• KBART for a whole provider usually means
manual holdings workflows is required
• A solution is needed to handle KBART
metadata at scale (too many providers)
Everything on
platform
Library
Package
Open Access
Content
Backfiles

51. Challenges
51
Libraries
• All title history isn’t included*
• Transfers are tricky; providers/vendors don’t update
coverage dates
• Lack of accountability; who needs to fix the problem
• Links break
• Files/collection contents are outdated
• Relevant collections not easy to find or don’t exist
• Working in a consortia environment is difficult
• No access to title in a package
• MARC records can lag behind
• Retracted rights, postponed publication, change of
subject collection
• OA titles not treated with same diligence
• Creating custom collections are too labor-intensive**
• Doesn’t cover all content types
Providers
• All title history isn’t in internal systems
• Transfers are tricky; providers don’t update
coverage dates
• Lack of accountability; who needs to fix the problem
• Erratic update schedules from vendors
• Disparate systems and teams
• Hundreds of collections to maintain
• Not enough internal resources
• Lack of vendor KB transparency
• Institutions have different needs for KBART
• Creating custom collections are too labor-intensive
• Difficulty finding vendor point of contact
• Doesn’t cover all content types
Vendors
• All title history isn’t included
• Transfers are tricky; providers don’t update
coverage dates
• Lack of accountability; who needs to fix the problem
• Provider overlays manually corrected data with incorrect
data
• Links break
• Files/collection contents are outdated
• Relevant collections not easy to find or don’t exist
• Retracted rights, postponed publication, change of
subject collection
• Erratic update schedules from providers
• Difficulty finding provider point of contact
* Bold bullets indicate challenge shared across stakeholders
** Bold, underlines and italicized bullets indicate planned solution

52. Solution (Institution-specific holdings)
52
KBART Automation
• Originally developed by Elsevier, adopted by OCLC and Ex Libris
• NISO working group included provider, vendors, and libraries
• Recommended Practice released June 2019
• Utilizes an API to send library holdings data from provider to vendor
• Libraries opt-in to sending their holdings to their vendor of choice
• No more manual work from libraries
• Current content provider participants: Wiley, Elsevier,
SpringerNature, JSTOR, Ovid, ProQuest, Rittenhouse
• Current vendor participants: OCLC and Ex Libris

53. Solution (For additional content needs)
53
KBART Phase III
• Expansion into new content types; textual and non-textual
• Globalization improvements
• Language
• Translated or transliterated title information
• Contributor names
• Supporting additional, optional, & dynamic file formats (JSON)
• Endorsement tiers for providers
• Investigation into improvements for hybrid OA and article-
level information
Phase I
(2010)
• Journals
Phase II
(2014)
•Books and
Conference
Proceedings
Phase III
(2022)
• OA,
Streaming,
Archives and
more

54. Solution (For package identification)
54
Unique Electronic Resource Package Identifiers
• The NISO Unique Electronic Resource Package Identifiers Working
Group will evaluate and create recommendations for a unique
identifier to enable disambiguation between packages, which can
be used across the supply chain.
• This identifier will allow all stakeholders to streamline and simplify
their processes, and to more easily track changes.
• Provide libraries with clear information about which titles a
package contains, enabling them, for example, to manage claims
when journals move between publishers.
• Representatives are welcome from across all stakeholder groups

55. KBART Resources
55
NISO/UKSG KBART Working Group. (2010). “KBART: Knowledge Bases and Related Tools.” Retrieved from
https://www.uksg.org/sites/uksg.org/files/KBART_Phase_I_Recommended_Practice.pdf
KBART Phase II Working Group. (2014). “KBART: Knowledge Bases and Related Tools Recommended Practice.”
Retrieved from https://www.niso.org/publications/rp-9-2014-kbart
NISO RP-26-2019, KBART Automation: Automated Retrieval of Customer Electronic Holdings. Retrieved from
https://groups.niso.org/apps/group_public/download.php/21896/NISO_RP-26-2019_KBART_Automation.pdf
Links to the latest information: https://www.niso.org/standards-committees/kbart
KBART for Content Providers (Style Guide, template files, etc.): https://www.niso.org/standards-
committees/kbart/kbart-content-providers
KBART Automation: https://www.niso.org/standards-committees/kbart/kbart-automation
KBART Interest Listserv: https://groups.niso.org/lists/kbart_interest/
Wiley KBART Page: https://onlinelibrary.wiley.com/library-info/resources/discovery/kbart2019

56. COUNTER
Ilda Cardenas
Electronic Resources Librarian
California State University - Fullerton
56

57. E-resource lifecycle – Evaluate and Monitor
57
https://www.nasig.org/Competencies-Eresources

58. COUNTER
History:
• Counting Online Usage of Networked Electronic
Resources
• Is a not-for-profit company based in the UK.
• COUNTER initiative was launched in 2002, to improve
the reliability of online usage statistics through codes
of practice.
• This standard has gone through various releases and
today the most current Code of Practice is Release
5.0.2 (Project COUNTER)
58
-Betty Landesman (2016) Taming the E-Chaos Through Standards and
Best Practices: An Update on Recent Developments, Serials Review, 42:3,
210-215, DOI: 10.1080/00987913.2016.1211443

59. What does COUNTER do?
• COUNTER usage statistics normalize usage data across
content providers for librarians.
• Project COUNTER works with platform providers and
publishers to ensure data is consistent and reliable.
Report types
• Platform reports: provide a summary of activity on a given platform to support the evaluation of platforms and to provide high-
level statistical data to support surveys and reporting to funders.
• Database reports: provide a summary of activity related to a given database or fixed collection of content that is packaged like
a database. These reports provide a means of evaluating the impact a database has for an institution’s users.
• Title reports: provide a summary of activity related to content at the title level and provide a means of evaluating the impact a
title has for an institution’s patrons.
• Item reports: provide a summary of activity related to content at the item level and provide a means of evaluating the impact
an item has for an institution’s patrons.
– From: Project COUNTER, Code of Practice (https://cop5.projectcounter.org/en/5.0.2/04-reports/index.html)
59
- Jill Emery, Lorraine Estelle & Stephanie J. Adams (2021)
COUNTER 5: Lessons Learned and New Insights Achieved, The
Serials Librarian, DOI: 10.1080/0361526X.2021.1884489

60. How is usage tracked?
60
Project COUNTER is flexible in terms of how usage activity is
logged but two approaches are:
• Log file analysis
• Page tagging
Other options:
• Distributed Usage Logging (DUL)

61. Sample COUNTER report
61

62. Closing
Ilda Cardenas
Electronic Resources Librarian
California State University - Fullerton
62

63. Impact of standards on ERM
• Standards allow a seamless transfer of data within and outside of the library
system you have.
• Standardization helps everyone whether publisher, vendor or librarians work
with electronic resources.
• Challenges are we do not understand how standards work and may
disregard how important they are.
• Without implementation amongst all information professionals, we risk
making up our own rules and creating more work for ourselves.
63

64. Questions
Ilda Cardenas
ildacardenas@Fullerton.edu
Beverly Geckle
Beverly.Geckle@mtsu.edu
Matthew Ragucci
mragucci@wiley.com