Aleph Product Working Group

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

description

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. - PowerPoint PPT Presentation

Transcript of Aleph Product Working Group

Page 1: Aleph Product Working Group

Aleph Product Working Group

Aleph PWG Business Meeting

Berlin, Sept. 9th, 2013

Page 2: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Aleph PWG Agenda

1) Aleph v23 Enhancement Process

2) Conference Planning

3) Aleph v22 Enhancements

4) Q & A

Page 3: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Enhancements 2013/20141) Detailed information about enhancements can be found in

http://igelu.org/products/aleph/aleph-enhancements

2) 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

Page 4: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Using NERS for ALEPH enhancements

1) New enhancements are submitted on NERS

2) Old enhancements submission should be demanded to Aleph

PWG

3) NERS database is shared by IGeLU and ELUNA

4) IGeLU members can vote on enhancements submitted by ELUNA

5) In IGeLU enhancement cycle, the enhancements already

accepted by ELUNA are removed from voting

6) Each member has 100 points for voting

Page 5: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Voting for 2013 Enhancements

IGeLU Aleph on NERS https://ners.igelu.org

Voting opens October 13, 2013

Page 6: Aleph Product Working Group

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

Page 7: Aleph Product Working Group

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

Page 8: Aleph Product Working Group

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?

Page 9: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Nominations and Voting for PWG members

Acquisitions/Serials (EDI)

Systems Administration

Page 10: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Enhancements approved in 2012/2013

1)40 enhancements were submitted for first voting cycle

2)The 15 most voted enhancements were selected for second voting

cycle

3)The 7 most voted enhancements were selected and sent to

ExLibris to be implemented in v22

Page 11: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Q & A

Page 12: Aleph Product Working Group

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.

1)Why can't we run rts64 instead of rts32 and take full advantage

of our 64-bit machines?

Page 13: Aleph Product Working Group

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

1)When ue_21 job be able to run multiple processes, like ue_01?

Page 14: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Question 3

1) Will be mandatory to re-index Aleph when migrating from

v21 to v22 an there are other major time-consuming steps in

the upgrade?

Page 15: Aleph Product Working Group

Aleph PWG Business meeting, Berlin 2013

Question 4

1) The logical "and" must be used to search several keywords

in SRU search. When be available a version to use keyword

search without "and"?

Page 16: Aleph Product Working Group

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.

1)When Exlibris plan to certify Aleph GUI for 64-bits windows

server (2008 and 2012), granting support for users who want to

use it?