[live-blog IGeLU Conference 2013, Berlin - please forgive typos etc.]
Q: Read-only access to the Alma configuration screens availability?
A: First let me explain what this is: it refers to the process during implementation, ExLibris performs the configuration in the first instance but once the customer has received the Certification Training, ExLibris doesn't do this anymore. This at the moment is near the end of the implementation just before Alma goes live. We've received this as an important feedback, that people want more transparancy and understand better the configuration options during implementation. By the end of the year we will have a read-only option for the configuration. This will first be at the fulfilment level. This will be incorporated as part of the permissions based on roles.
Q: Data quality and how to re-use cataloging already done is important. What is happening with the plans for the Alma community zone where we expect we should be able to find most records instead of searching them via external sources?
A: It's part of our key goals to improve efficiencies, focus on enabling streamlined sharing. We've started this by modelling this, we're at the stage where we work with the policies and cataloguing advisory group and expect to get results towards the end of the year. We presented the suggested model now and you will recognise real efficiencies in processes. We are finalising the development of those recommendations.
Q: Plans to share EzProxy configurations in the community zone?
A: The community zone isn't planned for that, but it's a good question and we should think about that.
Q: When can we expect to see license information in Alma's uResolver? (obligation to display copyright information in e-resources)? Will we ba able to rename fields or add local terms to be added to the uResolver copyright information when finally built out?
A: The option to show the licensing info is planned for the 2nd quarter of 2014. We will allow to adjust the wording of those fields to be more user friendly. This is in our roadmap.
Q: Cloud safety - What if anything happens to a Data Center? How will Ex Libris restore services to customers whose data and applications are housed in the Cloud?
A: We're aware that out Cloud is a lot of responsibility. We've looked at all the details for hardware, using the best hosting that we can find. We have 6 internet providers providing to the site, multiple firewalls, applications designed specifically and testing in that way. We've upgraded our backup, we used to do it on tape but now we do it on disc offsite. The ability to restore from there to another location would be much quicker than in the past. We have multiple ways to resolve such issues. It's easier to restore from site, but we can do it differently. Restoring is not a simple process. In a catastrophic situation, it would be less than a year... But more like a week...
Q: When can we finally expect daily analytics for Alma?
A: We've just announced that this is near release. It's been rolled out in 10 institutions of the US as part of the testing and it should be available to all customers by mid-October. The short answer is that it's already there.
Q: WorldShare Management Services is OCLC's response to Alma. Although Alma is more mature, given WorldCat as the primary cataloguing datase of WMS do youreally think it makes sense to build a second (semi-)global Bib library within Alma?
A: We want to build efficiencies in processes, not to re-build WorldCat, which was designed a few decdes ago. We're looking into the future. We want to integrate any existing service that is useful to you. Such environments includes WorldCat and this can be included in Alma. Wheter you're an alone-institution or part of a consortium, integration is possible. Others who don't work with WC may find new efficiencies in Alma.
Q: OCLC has recently published info about the WC metadata API. What about ExLibris, planning to integrate in Alma (looks like a good replacement for Z39.50)?
A: We've started discussion with OCLC about this, it's on its way
Q: UStat is the first SaaS component from ExLibris. How long will it remain as a separate product for sfx users? Will it's functionalities be integrated in Alma?
A: Alma anlytics will have greater functionalities
Q: Does Salesforce offer a Claud Status page in order to indicate when the servesr hosting Salsefoce CRM are down?
A: We will post in our Customer portal page the status of our services, including Salesforce
Q: The Ex Libris Customer Center platform is not easy to search, after developping such a good product like Primo, can we expect the same for the Customer Centre?
A: Priority is on services to users but we will look to improve the search engine for the Customer Centre next year
Q:With OA issues, this changes how content is made available. Ins SFX, with effect in Primo, we work at Journal level but OA is at article level, how will ExLibris manage this?
A: Part of our next linking project is to provide this info to the link resolvers
Q: Are e-book loans sheduled in any ExL software?
A: This is more of a question for vendors and we'd be interested to see vendors' models
Q: How far did the implementation of RDA in combination with Aleph & Alma proceed?
A: Voyager team work closely with the Library of Congress team, Aleph didn't need to do any configuraiotn work and Alma cataloguing support will be finalised in the next few months. Next steps: all eyes on on bibFrame but they've not agreed to implement FRBR they're working on a new model also don't think MARC21 should be the standard, so it's too soon to say on how we'll move forward on this question.
Q: Primo was launched as part of the strategy to decouple the frontend from the backend.Many primo services are availabolo only to Alma users and the front end of Alma *is* Primo, could you expand on this strategic shift to a monolithic (or symbiotic) couple?
A: It's tactical/pragmatic rather than strategic. The dicoupling process between front and back end are still relevant, both Primo and Alma can enable 3rd party component. Next gen framework is still relatively young, we develop a lot of user case but we still don't have enough best practice etc. but it will come. Tightly connected interaction between A & P is based on interfaces
Q: Marketplace for metadata requires cooperation between all parties. What about collaboration with EBSCO? Other discovery tools seems to be able to agree with each other to share data. Why not Ex Libris?
A: Good news is that it becomes more apparent what's going on and that EBSCO doesn't enable the subscription based index for discovery services such as Primo. You have to buy EDS to access EBSCO content so you are told to buy another discovery system. Otherwise it would be through API. Indexing is the best way to do it but they offer their service through API. This is a problem especially for those of you who pay for this content. We find it hard to find a way around it. In terms of other deals, when it comes to conent and aggregators such as EBSCO, their content is not unique and we are making good progress to provide alternatives. We sign deals with publishers.
No comments:
Post a Comment