...
The Resource Management SIG works with developers to define essential functions for acquiring and managing all types of materials: fund structures, orders, receiving, payment, claims, licensing, access and authentication methods, maintenance, usage and other statistics, other possible evaluation tools, and reporting. The SIG will consider options to show relationships between resources, and mechanisms and workflows needed to support these functions. The SIG will also need to evaluate the potential for applications supporting selection, decision-making, and analysis with the aim of ensuring that current work does not limit future innovation. The Resource Management SIG advises developers on the coordination needed between its operations and other functions, such as metadata management. It also advises developers on the interactions needed between libraries, vendors, and other parties necessary for successful resource management.
Current Structure
...
Because the topical area covered by the RM SIG Resource Management is so large, work is divided into separate groupsSIGs. There are two three main groups SIGs that are currently active:
Acquisitions
...
SIG
The Acquisitions Subgroup is charged with working with developers to develop, refine, and review the acquisitions functionality and user experience. Members, generally acquisitions specialists, commit to regular meeting attendance, and to work on projects and tasks outside of meeting times that contribute to the requirements definitions, refinement, user experience improvements and testing. Members are expected to stay current with pertinent topics in order to keep discussions moving forward. Meeting notes are available on the wiki.
...
Product Owner: @Dennis Bridges
ERM
...
SIG
The ERM Group is charged with working with developers to develop, refine, and review functionality needed to support the management of library electronic resources. This includes Agreements, Licenses, and eResources. Members, generally e-resource management specialists, commit to regular meeting attendance, and to work on projects and tasks outside of meeting times that contribute to the requirements definitions, refinement, user experience improvements and testing. There will also be regular meeting time devoted to implementation topics raised by the members. Members are expected to stay current with pertinent topics in order to keep discussions moving forward. Meeting notes are available on the wiki.
...