Difference between revisions of "Trip Report: 4th IGeLU Conference, Helsinki, 6-9th September 2009"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 46: Line 46:
== Tuesday, 8th September 2009 ==
== Tuesday, 8th September 2009 ==
=== Aleph PWG Business Meeting ===
=== Aleph PWG Business Meeting ===
Gerard Bennett
'''Report of Gerard Bennett'''
* collaborative testing of v20 in January 2009
* collaborative testing of v20 in January 2009
* new version release policy with v20<br>Major releases delivered on schedule, take-up in UK, US, Italy, Australia, South Africa<br>Minor release v20.1: will include significant enhancements, delivered by ServicePacks mechanism<br>The new policy enables to implement enhancement faster - at least that's the hope<br>Timeline: V21 2011, V22 2013; no commitment for the time beyond from Ex Libris
 
* new version release policy with v20
** Major releases delivered on schedule, take-up in UK, US, Italy, Australia, South Africa
** Minor release v20.1: will include significant enhancements, delivered by ServicePacks mechanism
** The new policy enables to implement enhancement faster - at least that's the hope
** Timeline: V21 2011, V22 2013; no commitment for the time beyond from Ex Libris
 
* Communication with Ex Libris
* Communication with Ex Libris
** Monthly conference calls with product manager (Eluna / Igelu  SC/APWG)
** Monthly conference calls with product manager (Eluna/IGeLU and SC/APWG)
** Topics: version release, enhancements, testing, URM
** Topics: version release, enhancements, testing, URM
** Commitment that they could report more to the community
** => Commitment that PWG could report more to the community about the content of this calls


* Collaboration with eluna
* Collaboration with ELUNA
** Meetings
** Meetings
** Coord in enhancement
** Coordination of enhancements
** NERS system for more collaboration, both enhancement together can be seen
** NERS system enables more collaboration; enhancements of ELUNA und IGeLU can be seen on one platform
 
*Focus group work in URM, e-Books management
 
 
Mike Ryan: Aleph-Enhancement Coordinator
Formerly: annual process for every release
Now also minor releases, 120 points per year no matter if major or minor, just was gerade ansteht, can be faster now
Specifications go back to us (did exl understand the enhancement the right way?)
V20.0: 1637, 1583, 1668,…
V20.1: 1585, 1595, 1596,1614,1725
 
Zusammenfassen, damit’s wichtiger wird
 
Marcus Zerbst
Website: not happening very much, wishes?
Information can be protected, members only
Intention to make it more interactive, e.g. blogs
 
El commons: growing slowly
Dev zone comparatively active
Encourage to use the wiki, the space


ARC
* Focus group work in URM and e-Books management
Communication with exl
ARC enhancement poll


NERS
'''Report of Marcus Zerbst'''
AlephPWG also involved
* Website
** in the moment not happening very much; are there wishes?
** Information can be protected for members only
** Intention to make it more interactive, e.g. blogs


2 new members searched
* El Commons
** growing slowly
** Developer zone comparatively active
** => Encouragement to use the wiki and it's possiblities


Befürchtung, dass exl die enhancements für urm nutzt
The Aleph-PWG is looking for 2 new members.


=== URM and Strategy Update, Kathryn Harnish ===
=== URM and Strategy Update, Kathryn Harnish ===

Revision as of 11:25, 15 September 2009


Monday, 7th September 2009[edit]

IGeLU Update[edit]

338 members in 38 countries; stable prices for membership

  • new Primo Product Working Group (PWG)
  • surveys about expectations on next generation products planned
  • cross product activities
  • new enhancement platform (NERS)

Ex Libris Report, Matti Shem Tov[edit]

Ex Libris Product Update Summary, Oren Beit-Arie and Nancy Dushkin[edit]

The OPAC is dead - Long live the OPAC - workshop, Daniel Forsmann[edit]

The aim is to make yourself aware of what you want and what you need in order to judge which product fits best and to be able to make the right decision for a discovery tool.

In advance the participants had to answer the following questions (The scale in questions 1 - 14 is 1 - 10 where 1 is the worst and 10 is best.):

  1. How happy are you with your current OPAC?
  2. How important is it to enrich the OPAC with external content (for instance forwarding searches, table of contents, covers, Google Books, integration with union catalogs, databases, Library Thing)?
  3. How important are RSS feeds in the OPAC?
  4. How important is it to be able to search the OPAC from other sources like Facebook, iGoogle, Netvibes ... ?
  5. How important is tagging in the OPAC?
  6. How important are user generated reviews and comments in the OPAC?
  7. How important are librarian-generated reviews and comments in the OPAC?
  8. How important are clustering of search results in the OPAC?
  9. How important is it to be able to do federated searching in selected databases/digital archives/institutional repositories from the OPAC?
  10. How important is it to to embed the OPAC into the library website (graphics and navigation)?
  11. How important is it to integrate link resolvers (like SFX) into the OPAC?
  12. How important is your access to the OPAC server and configuration?
  13. How important is it to make the catalog data available for external indexing (OAI-PMH, permanent URL:s for Google indexing)
  14. How important are OPAC API:s?
  15. Mention five features in you current OPAC that you apreciate. Please motivate, but keep short.
  16. Mention five features you miss in you current OPAC. Please motivate, but keep short.
  17. List up to 10 OPAC that you find inspiring or worth mentioning. Please motivate, but keep short.
  18. List up to 10 library websites that you find inspiring or worth mentioning. Please motivate, but keep short.

The presentation summarizes the results: http://www.slideshare.net/halwete/the-opac-is-dead-long-live-the-opac

Some explanatory notes of Daniel:

  • important to present your content in your local environment, e.g. library website
  • important to be able to present your content within an interface where the user wants it (using APIs)
  • making people aware of that we (the library) exist, by being present with e.g. search boxes in facebook, although it's perhaps not used

Tuesday, 8th September 2009[edit]

Aleph PWG Business Meeting[edit]

Report of Gerard Bennett

  • collaborative testing of v20 in January 2009
  • new version release policy with v20
    • Major releases delivered on schedule, take-up in UK, US, Italy, Australia, South Africa
    • Minor release v20.1: will include significant enhancements, delivered by ServicePacks mechanism
    • The new policy enables to implement enhancement faster - at least that's the hope
    • Timeline: V21 2011, V22 2013; no commitment for the time beyond from Ex Libris
  • Communication with Ex Libris
    • Monthly conference calls with product manager (Eluna/IGeLU and SC/APWG)
    • Topics: version release, enhancements, testing, URM
    • => Commitment that PWG could report more to the community about the content of this calls
  • Collaboration with ELUNA
    • Meetings
    • Coordination of enhancements
    • NERS system enables more collaboration; enhancements of ELUNA und IGeLU can be seen on one platform
  • Focus group work in URM and e-Books management

Report of Marcus Zerbst

  • Website
    • in the moment not happening very much; are there wishes?
    • Information can be protected for members only
    • Intention to make it more interactive, e.g. blogs
  • El Commons
    • growing slowly
    • Developer zone comparatively active
    • => Encouragement to use the wiki and it's possiblities

The Aleph-PWG is looking for 2 new members.

URM and Strategy Update, Kathryn Harnish[edit]

Wednesday, 9th September 2009[edit]

Reviewing & improving - our job is never done?[edit]

URM Development Partnerships: A Panel Discussion[edit]

Ex Libris General Q&A[edit]

Resources to follow the conference online[edit]