Development of the Collection Governance Framework
Deakin Library’s collections contain over 650,000 physical items across four Australian campuses and a small collection at our offshore campus in India. Our users have access to over 1,000,000 e-books, over 220,000 e-journals, almost 600 databases, over 360,000 streaming media sources, as well as 16 Read and Publish agreements which are negotiated through our national consortium, the Council of Australasian University Librarians (CAUL).
After major organizational change in late 2022, Deakin Library’s established collection governance structures and decision-making processes based on hierarchical committee structures were discontinued. Additionally, no comprehensive collection governance review or collection assessment and maintenance program had been undertaken in several years despite significant changes in the higher education and academic library sectors, making a comprehensive collection review a high priority.
The strategic Deakin Library Plan 2022–2025 provided guidance throughout the process and acted as major catalyst for the development of Deakin Library’s new Collection Governance Framework starting in early 2023.1 The main aims for the development and implementation of the framework and collection strategy were:
Values-driven: Align with Deakin Library’s human-centered strategy through a values-driven approach. Our goal was to focus on ethical and proactive decision-making, not only to ensure the best fit for purpose collections for our Deakin communities but also to challenge the status quo of established systems and business models.
Efficient: Replace the old collection governance structure, which was heavily dependent on meetings with rigid and exhaustive documentation requirements that often required significant workloads and resulted in delayed decision-making. Develop an innovative, agile, and efficient approach and replace manual workflows with automation as much as feasible.
Transparent and collaborative: Build a comprehensive collection evaluation process that incorporates transparency of responsibilities and information throughout, and provides proactive, robust, and efficient collection development and management practices while empowering staff across the library to contribute to collection governance and maintenance.
Fit for purpose: Ensure that our resources are fit for purpose to support Deakin communities’ learning, research, innovation, and a sense of community and belonging. Ensure we avoid resource acquisition and retention for “just in case” or preservation and aim for our collection to be hardworking, demonstrating a strong and consistent use of resources.
Open: Prioritize open research and open infrastructure where feasible.
Diverse and inclusive: Embed diversity and inclusivity not only through the subjects and content acquired, but also in our metadata and discovery strategies, improved accessibility through a wide range of resource formats and support services, and Indigenous Knowledges programs.
Deakin Library’s Collection Governance Framework is based on three distinct layers:
Collection Values form the foundation for the Framework.
Collection Principles outline in practical terms how the collection values are applied practically to both manage our collections and provide collection services more broadly.
Collection Evaluation Criteria measure resources against the values and principles.
Figure 1 provides a summary overview of the framework.
Collection Evaluation Rubric
Our original intention in building a scorecard for collection evaluation based on our collection evaluation criteria was quickly superseded by a rubric model. As a well-established assessment and evaluation tool in higher education, a rubric would be familiar to our key stakeholders and offer the advantage of being more flexible and nuanced than a scorecard and allow us to more easily combine qualitative with quantitative assessment.
The narrative-based structure of the rubric facilitated input from subject matter experts using their expertise and own language to define the criteria in their relevant sections and foster strong collaboration between teams and ownership of the process. This also enabled an element of subjectivity in the evaluation while still ensuring consistency in the assessment process, allowing for what was previously considered a gut feeling to be expressed in a more formalized and evidence-based manner. Through this process we were able to introduce discipline-specific nuance within the broader evaluation criteria, balancing quantitative criteria like CPU against qualitative criteria like relevance and quality of the resource for the relevant disciplines. This balance is deeply embedded and maintained in the rubric through scoring and weighing each of the criteria against each other with different importance assigned to different criteria depending on the type of resource.
To ensure the rubric reflects the various perspectives and needs of various stakeholders, the team ran a program of workshops with all relevant library teams to capture the expertise and opinions of all teams who would be contributing to resource evaluation.
It took over six months of workshops, drafting, revising, reviewing, and testing to complete the rubric in its current form. While the framework is very comprehensive, resources are not assessed against every single criterion in the rubric. As Table 1 below shows, resources are only assessed against criteria considered relevant, and depending on the cost of a resource, the criteria are more or less strictly scrutinized. There are also a number of criteria designated as critical for decision-making; if any of these criteria rates below the acceptable level, an in-depth review is initiated to consider the impact of the low rating for the overall purpose of the resource for the university.
Rubric |
Collection Performance Criteria |
Initiate in-depth review if rating is low |
Physical Collections |
Electronic Resources |
Research Tools & Resources |
Publishing Agreements |
Library Working Tools (internal use) |
High-value Donations |
Digitization Projects |
Sector Memberships and Support |
|---|---|---|---|---|---|---|---|---|---|---|
Alignment with Deakin Strategy, Vision and Values |
Strategic Alignment |
✸ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Vendor Conduct and Commercial Integrity |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
Membership Benefits |
✕ |
✕ |
✕ |
✕ |
✕ |
✕ |
✕ |
✔ |
||
Disciplinary Field |
Supports Research & Teaching |
✸ |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
✔ |
✕ |
Reputation |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
✔ |
✕ |
||
Collection Strength and Relevance to Deakin University History |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
✔ |
✕ |
||
Licensing and Compliance |
Compliance |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Authorized Users |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✕ |
✕ |
✕ |
|
Terms and Conditions of Use |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✔ |
✕ |
✕ |
|
Privacy |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
|
Liability |
✸ |
✕ |
✔ |
✔ |
✔ |
✕ |
✔ |
✕ |
✕ |
|
Administration |
Resourcing |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
Customer and Technical Support |
✕ |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
✔ |
||
Agreement Administration |
✕ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✕ |
||
Cost and Usage |
Cost Benefit |
✸ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Reporting |
✕ |
✔ |
✔ |
✔ |
✔ |
✕ |
✕ |
✕ |
||
Metadata and Discovery |
Authentication |
✸ |
✕ |
✔ |
✔ |
✔ |
✔ |
✕ |
✕ |
✕ |
Access |
✕ |
✔ |
✔ |
✔ |
✕ |
✔ |
✕ |
✕ |
||
Discoverability |
✔ |
✔ |
✔ |
✔ |
✕ |
✔ |
✔ |
✕ |
||
Usability and Accessibility |
Usability |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✕ |
|
Accessibility |
✕ |
✔ |
✔ |
✔ |
✕ |
✕ |
✕ |
✕ |
||
Publishing |
Impact on Deakin’s Open Access Agenda |
✸ |
✕ |
✕ |
✕ |
✔ |
✕ |
✕ |
✕ |
✕ |
Publishing Journey |
✕ |
✕ |
✕ |
✔ |
✕ |
✕ |
✕ |
✕ |
||
Rights Retention |
✕ |
✕ |
✕ |
✔ |
✕ |
✕ |
✕ |
✕ |
Implementing and Structuring the Evaluation Framework in Jira
In operationalizing the rubric, it was essential to align with the values underpinning the framework and find a software solution that would complement existing workflows and improve efficiency where possible. The chosen platform was Jira, a project management tool from Atlassian. Jira is widely used in the software industry to support various agile methodologies, including Scrum and Kanban, and is highly customizable to accommodate diverse project workflows. Key features such as agile boards, backlogs, roadmaps, and reporting enable efficient and collaborative project management.
For this implementation, a shared digital workspace was required that allowed for collaboration across multiple teams and individuals with the flexibility to involve contributors on an as-needed basis. Transparency was also a critical consideration; it was important that evaluations be visible across teams to ensure that decision-making moved beyond closed committee processes and became more accessible to all library staff. Finally, a single source of truth was required: a stable, central location in which all discussions, evaluations, and decisions could be recorded and accessed year after year.
To implement the rubric in Jira, a Parent-Child issue hierarchy was implemented. The Parent issue provides a central overview of the resource, while each Child issue corresponds to a specific rubric section where criteria are assessed. This structure enables distributed evaluation, allowing teams to focus on areas aligned with their expertise.
To support transparency and usability, each Parent issue includes several key components: general instructions, a resource description, and essential metadata such as publisher, vendor, purchase history, discipline, and other administrative details. Custom fields and controlled vocabulary are used where possible to ensure consistency in data entry. A prominent Approval Progress section provides a concise summary of the review status, including approvals, decision-makers, associated costs, and planned review dates. All associated Child issues are listed along with hyperlinks for ease of navigation.
Child issues inherit resource metadata through Jira automation and updates made to the Parent issue cascade down to the Child issues to ensure consistency. The primary evaluation activity occurs within the rubric criteria section, where each item is assessed using a drop-down list aligned with a six-point scale from unacceptable to ideal. A comments section allows evaluators to provide contextual notes or justifications for their ratings. Jira also supports ongoing contributions beyond formal review cycles where users can add comments or revise ratings in response to new information, such as user feedback, vendor announcements, or curriculum changes.
Jira Workflows and Automations
Customization of the Jira project and the integration of automation have enabled streamlined and manageable workflows to support the evaluation process. The workflows align with three main streams of activity: work completed by the Collections Team, automation-driven processes, and contributions from other library teams involved in resource evaluation.
The full workflow begins with the creation of a Parent issue, followed by the automated generation of relevant Child issues based on resource type. Metadata is inherited, and non-applicable criteria are automatically flagged. The Collections Team then assigns Child issues to specialist teams, initiating the evaluation phase.
Automation supports key transitions throughout the process including triggering evaluation notifications, monitoring completion, reallocating issues for analysis, and alerting stakeholders at critical points such as final approval. Manual quality checks, final decisions, and actions such as renewal or cancellation are completed by the Collections Team. A final automation resets the Jira issues in preparation for the next review cycle. Figure 2 shows the workflows between the Collections Team, the Jira automations, and the contributions by other library teams.
Integration with Confluence and Visualizing Evaluation Outcomes
Progress and status are monitored using Jira’s visualization tools, including timelines and dashboards, which can be filtered by various controlled vocabulary fields. An integration with Atlassian’s Confluence product provides each library team with a dedicated dashboard displaying their outstanding Child issues. These dashboards are generated using a simple saved search embedded in Confluence, allowing teams to track and manage their tasks, focusing on their assigned issues in isolation, improving usability and reducing cognitive load.
Tableau is used to analyze and visualize evaluation outcomes at the individual issue level. Figure 3 shows a dashboard example with an overview of evaluation progress, approval status, and outcomes.
Resource details are displayed in a format consistent with Jira to support decision-making. A preliminary outcome is generated based on the rubric six-point scale and weighting by resource type, providing an initial recommendation. A low rating alert highlights any unacceptable criteria, prompting review of supporting comments.
Section-level results are visualized using a red-to-green gradient aligned with the rating scale. This traffic light system offers a quick, intuitive view of evaluation outcomes, with the same color logic applied to the recommendation, and text is provided to ensure accessibility for all users.
Impact, Learnings, and Insights
The impact of the implementation of the new Collection Governance Framework is a more structured and consistent approach to collection assessment with a single source of information in Jira. This has resulted in more immediate communication and consultation between teams, leading to a more efficient and timely decision- making process.
Efforts are ongoing to further streamline the framework and simplify the associated workflows. Following the completion of a full evaluation cycle, there will be an opportunity to undertake benchmarking such as comparing resources by discipline, format, or cost bracket. We are also actively investigating opportunities for automation through the use of APIs to facilitate data integration.
While the initial setup has been quite time-consuming, we have already seen significant time-savings as staff can add comments and contribute to the evaluation process at any time, cutting down on e-mails and meetings. As this process matures even further, evaluations will simply need to be reviewed during the normal review cycles and only updated if significant changes have occurred, saving even more time.
Setting up Jira required substantial self-directed learning, particularly in building a new project. In hindsight, mapping out fields, workflows, and automation logic in advance would have reduced time spent on revisions during configuration.
Despite early consultation with teams, a delay between planning and implementation led to knowledge gaps. This underscored the need for ongoing support and training, especially for staff not involved in the initial development phase.
The framework and the completed evaluations have also enabled us to form much more robust and informed negotiation strategies, leading to the cancellation and rejection of purchases not only due to unsustainable and unjustified price increases, but also due to a misalignment with our values and principles and ethical concerns.
Acknowledgments
We would like to acknowledge the contributions of our Deakin University colleague:
Lauren Halcomb-Smith, Lecturer, Open Education, at Deakin University for the collaborative development of the Deakin Library Collection Governance Framework.
Danny Kingsley (Director, Library Services (Information)), Catherine King, (Manager, Licensing and Subscriptions), and Skye Ryan (Manager, Monographs and Course Resources) for their support in preparing this session.
Contributor Notes
Anna Rubinowski is Senior Manager, Collections, Deakin University, Geelong, Victoria, Australia.
Wendy Campbell is Collection Performance Librarian, Deakin University, Geelong, Victoria, Australia.
Note
- Deakin Library, Deakin Library Plan 2022–2025 (Geelong: Deakin University, 2024), https://www.deakin.edu.au/library/about/library-plan. ⮭



