50min | Recording Perpetual Access details for agreements | Owen Stephens | Recording Perpetual Access for an agreement ERM SIG discusses Heiko’s comment in the doc: According to Robert’s common scenario above, or in an EBA model – where you can often access all, or at least many, titles from a publisher for a certain period of time (during which data is collected) – let’s call this the information phase. In the information phase, no title is perpetual; only after this period do the chosen ones become perpetual. It’s good to keep that in mind. Usually, nobody notices as long as the titles are available – but when they’re gone… ;)
How could this be represented? Sara: You could have AGLs for those EBA Titles that become Perpetual Felix: I think in Heiko's scenario I'd work with 2 agreements, one during the running phase of the EBA and the other one for recording the acquired titles. But it's easy for me to say that, given at ZBW we have canceled our EBA stuff. Sara would do it differently from Felix. Same Agreement, but multiple AGLs Margaret: This is also what I would do (am currently doing!) with a custom package in HLM Sara: would manage in the way the data is managed in orders and Inventory Felix: The reason why I'd go with different agreements is that I want to know that the linked license is always representing the valid terms during acquiring the single titles. Maybe we would end up with n AGR over time for the single e-resources. But that depends on the licensing details of the vendor. Margaret: Can you make a distinction with multiple licenses attached to one agreement? One is current, one is historical? Felix: You can have one current license, but what if this new license only applies to the large EBA catalog, not the titles that you've acquired 5 years ago? You can't have a license on AGRLine level.
Margaret: would probably put not perpetual until first individual title is purchased; depends on what ACQ team decides to do with the POL Sara would mark it perpetual right from the beginning Becca: At Smith we’d create a separate agreement for the EBA itself and for the perpetual titles and then link them and then mark them accordingly (perpetual/non). So basically what Sara is saying! Heiko: all described ways of dealing with EBA make sense and can be worked with
Mechanisms = mechanics by which perpetual access is granted under an agreement Felix suggests: type Sara suggests either type or basis Owen prefers basis Felix: 'Basis' would work as well for me.
Margaret: maybe ownership model or access model (to avoid the term ”ownership”) Heiko: like this ownership and access model terms Philip: I would want to record the access model to help with troubleshooting when things go wrong. - Sara and Becca agree Becca: I agree with Philip, and it also helps us audit our metadata and ensure everything is tracked over time (if there is migration or staff turnover for example) - Sara agrees Philip: I think I am committed to buying something as a result of starting an EBA. So it could be perpetual Access Agreement with zero titles during the information Phase. - Sara and Heiko agree Maybe need to reverse mechanism and perpetual access List of mechanisms could be configurable - but then no logic can be build around it Alternative: make the list as complete as possible and adjust if necessary over time - but make it a hardcoded list Sara: streaming video related terms are missing Owen: would streaming video either be a EBA od PDA model? Sara: it’s about titles that are not part of packages; provided on a platform (hosted model) or via a file; but term outright purchase doesn’t sound right; especially when library is responible for the file and hosts file themselves → indicating responsibility of this perpetual access is important; but Sara sees it as perpetual access as they do not need to re-purchase Bernd: wonders whether it’s really worth making it hardcoded for a workflow that we might never agree on Felix: We distinguish between archiving and, if applicable, subsequent hosting in the trigger event and perpetual access. Philip: We are members of the Global LOCKSS Alliance and so have perpetual access to some subscribed content, but this would not fit under the current list of perpetual access mechanisms. How about Digital Preservation (DP)? Sara: & Portico Becca: And vendors are always trying to find new ways to sell things to us! (‘Enhanced’ content, etc) Philip: They are different: I might want to log my EBA purchases as being backed up by my Digital Preservation system.
|