Verde product update
Verde 2 roadmap
Verde SFX functionality
Verde 2 > Alma roadmap
Alma is almost here; Verde customers will receive Alma E functionality for no additional license fee - maintenance payment will be converted to subscription with the addition of cloud-related costs (this has not changed from previous Ex Libris statements). Existing Ex Libris customers will have preferred financial terms.
Committment to Verde hasn't flagged:
Continued to implement, maintain and support Verde 2
Quarterly SPs and monthly KB updates - have not been doing SPs recently because of SFX upgrade to v4
Support centralized COUNTER reporting service, UStat; continued to enhance service:
SUSHI support: April 2010
Cost per use conceptual design in progress; targeting late 2011 for implementation
Continued to support integration with SFX
KB harvesting mechanism released early 2011 with SFX 4.1
In the meantime...
Verde continues close association with SFX; SFX 4 is very different, so Verde has been in a bit of a holding pattern.
In Verde 2 / SFX 3, separate update packages were applied; sync occurred in the direction of Verde > SFX. In this model Verde/SFX must be in constant sync.
In Verde 2 / SFX 4:
Weekly SFX KB updates pushed; global KB changes + local changes and activations are published and harvested to Verde - information changed in SFX is read-only in Verde; can't get the two products out of sync that way. Can create local items in Verde but these won't show up in SFX.
No sync anymore - actions are now "publish" (in SFX) and "harvest" (in Verde).
System driving the KB is SFX 4
To avoid confusion, in Verde fields applying to "activation" function are read-only for global data and data created in SFX.
Local, EJournal, and package data, if not in global KB, should be created in SFX
Local records can be created in Verde for management purposes but these will not be visible in SFX.
SFX KB Update reports should be used to check additions/changes
Harvest is done in the backgroud; can be ongoing
Verde UI indicates havest status and date/time of last harvest
Do this work in SFX 4:
Update activation status
Unpate institution/library settings
Update coverage/embargo information
Create local portfiolios/targets for use as e-constituents/e-packages (if desired)
All SFX data carried to Verde and read-only:
--Global SFX ID
--Local SFX ID
Do this work in Verde:
Management data - all attributes
Deep link from Verde to SFX Admin for specific e-products
SFX menus can be generated from Verde
License info stored in Verde can be visible from SFX menu (e.g.: for ILL staff)
Status of upgrades:
SFX4.1/Verde SP released in Feb 2011
2 beta testers; 14 sites now upgraded, 3 in process of upgrading
Plan several weeks in advance; contact support to obtain SFX 4 license and receive pre-upgrade tips
More details: high-level document in the customer center
3 lessons in the Learning Center (key is available if not Learning Center subscribers)
Also upgrade guide and interoperability guide in documentation center - integration section
Also RE upgrade - if want Support to do it (all, half, etc), contact them
Manages COUNTER vendor usage for JR1 and DB1
Load data manually or via SUSHI (for some vendors)
Not all vendors support SUSHI; even for "SUSHI-compliant" vendors Ex Libris needs to do work to make sure vendor data loads correctly since SUSHI is a loose standard
NISO SUSHI Server registry - encourage vendors to include their SUSHI information on this registry
UStat 2011 plans:
Add more vendor SUSHI support (partially complete)
Support for COUNTER Code of Practice release 3 for DB1 reports (complete)
Cost per use - conceptual design now in progress
Like Verde, UStat will become part of Alma
Encouraged to go to Alma E (and to do along with Alma P - this is where the benefits are); no end of life plans for Verde