html5-img
1 / 16

Aleph Product Working Group

Aleph Product Working Group. Aleph PWG Business Meeting Berlin, Sept. 9th, 2013. Aleph PWG Business meeting, Berlin 2013. Aleph PWG Agenda. Aleph v23 Enhancement Process Conference Planning Aleph v22 Enhancements Q & A. Aleph PWG Business meeting, Berlin 2013. Enhancements 2013/2014.

takoda
Download Presentation

Aleph Product Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Aleph Product Working Group Aleph PWG Business Meeting Berlin, Sept. 9th, 2013

  2. Aleph PWG Business meeting, Berlin 2013 Aleph PWG Agenda • Aleph v23 Enhancement Process • Conference Planning • Aleph v22 Enhancements • Q & A

  3. Aleph PWG Business meeting, Berlin 2013 Enhancements 2013/2014 • Detailed information about enhancements can be found in http://igelu.org/products/aleph/aleph-enhancements • Timeline for enhancements • Sept. 20, 2013: NERS database is closed to new enhancement requests • Sept. 21 – Oct. 12: PWGs clarify and validate requests • Oct. 13 – Oct. 26: First voting period • Oct. 27 – Nov. 24: ExLibris assigns development points to enhancements • Nov. 25 – Dec. 29: PWGs work with ExLibris to clarify requests and pointing • Dec. 30 – Jan. 17, 2014: Final voting cycle • Jan. 18 – Jan. 24: PWGs select final enhancements to submit to ExLibris • Jan. 25 – 30: Remove ELUNA enhancements sent to ExLibris. • Jan 31: PWG submit final enhancements to Ex Libris

  4. Aleph PWG Business meeting, Berlin 2013 Using NERS for ALEPH enhancements • New enhancements are submitted on NERS • Old enhancements submission should be demanded to Aleph PWG • NERS database is shared by IGeLU and ELUNA • IGeLU members can vote on enhancements submitted by ELUNA • In IGeLU enhancement cycle, the enhancements already accepted by ELUNA are removed from voting • Each member has 100 points for voting

  5. Aleph PWG Business meeting, Berlin 2013 Voting for 2013 Enhancements IGeLU Aleph on NERS https://ners.igelu.org Voting opens October 13, 2013

  6. Aleph PWG Business meeting, Berlin 2013 Conference planning • Conference committee ≠ PWG • Monthly conference calls, hundreds of emails • Google Docs for collaboration • Late changes and very late changes

  7. Aleph PWG Business meeting, Berlin 2013 Conference planning • Aleph track Berlin 2013 • Networked GUI scenarios, • Systems merge, • Aleph Direct experiences, • ARC report studio, • copy-specific information in Aleph and Primo • Q&A

  8. Aleph PWG Business meeting, Berlin 2013 Conference planning • Aleph in Alma • SaaS instead of local installation • from pilots to regular migration • do we (want to) find our Aleph workflow?

  9. Aleph PWG Business meeting, Berlin 2013 Nominations and Voting for PWG members Acquisitions/Serials (EDI) Systems Administration

  10. Aleph PWG Business meeting, Berlin 2013 Enhancements approved in 2012/2013 • 40 enhancements were submitted for first voting cycle • The 15 most voted enhancements were selected for second voting cycle • The 7 most voted enhancements were selected and sent to ExLibris to be implemented in v22

  11. Aleph PWG Business meeting, Berlin 2013 Q & A

  12. Aleph PWG Business meeting, Berlin 2013 Question 1 • We are running on ALEPH 21 with COBOL5 and rts32 is the main routine for aleph server processes and our platforms are 64-bit machines since long time. • Why can't we run rts64 instead of rts32 and take full advantage of our 64-bit machines?

  13. Aleph PWG Business meeting, Berlin 2013 Question 2 • The enhancements in Aleph 21 for more scalability (e.g. multi server topology, splitting of UE_01 in multiple processes) were really good things for big installations. However there are still some vital parts in the system, which must also be scalable. If, for example, the UE_21 can not handle the same amount of data as the UE01, there will inevitably be problems of acceptance concerning the use of Primo • When ue_21 job be able to run multiple processes, like ue_01?

  14. Aleph PWG Business meeting, Berlin 2013 Question 3 • Will be mandatory to re-index Aleph when migrating from v21 to v22 an there are other major time-consuming steps in the upgrade?

  15. Aleph PWG Business meeting, Berlin 2013 Question 4 • The logical "and" must be used to search several keywords in SRU search. When be available a version to use keyword search without "and"?

  16. Aleph PWG Business meeting, Berlin 2013 Question 5 • Session 4.1 shows the full benefits on TCO for libraries running the Aleph GUI on a Windows Terminal Server. • When Exlibris plan to certify Aleph GUI for 64-bits windows server (2008 and 2012), granting support for users who want to use it?

More Related