Welcome, Opening Remarks, State of egils & Opening Keynote Intro

Opening Keynote

How to Translate Developer: A Live Translation Session

Support and Training in a Consortial Environment

Evergreen Serials: Making it Work For You

Action Triggers

In Search of Search

Contributing Code to Evergreen is Easier Than You Think

Lightning Talks

Envisioning Evergreen: Charting the Course to 2020

Welcome, Opening Remarks, State of egils & Opening Keynote Intro

Tara Robertson, Kathy Lussier & Brian Owen

Kathy Lussier -

The Year in development

Documentation:

Why should you contribute to the community?

Get involved

Milestone - One of our own - 2013 Mover & Shaker - Galen Charlton, @gmcharlt

Brian Owen (SFU) - Keynote intro

What do these stories have to do with open source development?

Opening Keynote

John Vaillant

How I became a believer in Open Source:

Comments and questions

How to Translate Developer: A Live Translation Session

Grace Dunbar & TBD

Lesson 1:

        What do developers mean by “some, all, most” in terms of code?

        They mean something...but what?

        Discusses framing problems in mutually respectful ways.

Bug reports are important instances of communication

Lesson 2:

        Developers are WYSIWYG

        What is the developer doing?

        Ask the right questions

                -good questions are specific and don’t interrupt or take up time

                -recommends “rubber ducking,” that is , asking the question out loud.

Lesson 3: How to make a developer’s head explode:

        “Mike, the search isn’t accurate enough,” when precision is the correct term.

        -Words have meanings:        

                Be specific

                Be thoughtful

                Be courteous

                Be descriptive

Argues that a developer’s job is to solve problems, writing code is the means to that end.  Developers are creative people: they enjoy making useful things.  Developers are more like architects than contractors; artisans not imitators.  The role of developers is to build nifty things, but it is not to train how it is used

Librarians aren’t just users, they are knowledgeable professionals, who are also problem solvers.

Q: how much do developers think about the performance of features once it is released into the real world of users.

A: some think about it a lot, others less so.  THe amount of time spent with specific tools is important.  Developers emphasize completing features.  This may be changing, IRC has turned increasingly to emphasizing performance.  Time-outs are improving and will continue to get better.

Q:  What is the average or reasonable response for bug  fixes?  Libraries can’t afford to be down.

A: While the open-source community isn’t fundamentally commercial, vendors are evolving to provide support and solve problems quickly.  Academic libraries cannot afford to be down.

        Audience comment:  from the IU community says the support has been pretty robust and the community can in many cases answer questions.

        Audience comment: Evergreen has has fewer critical issues than a previous proprietary service.  

        Audience comment: The support from Sitka has been 24/7 and amazing.        

Support and Training in a Consortial Environment

Shannon Dineen & Shauna Borger (Evergreen Indiana.)

        -Calls for organized collaboration between in the training community.

.

        Formal training:

                Core curriculum of Evergreen classes

                -Basics: circulation, cataloging, holds and searching, admin/reports.

                -trainers are trained to a set of standards and skills.

                -libraries send 1-2 staff

-server training

        Group discussions:

                Five committees on policy and training

                        Executive, cataloging, patron services, IT, eContent

                Rotating membership allows for new members to have new opportunities to learn & contribute.

                Provides social learning community for staff

                List-serves:

                        tips

                        is like a form of documentation

                Weekly Update blog

Individual training

        One-on-one consultation and training.

                reinforces learning from  the training seminars

        Regional Coordinator (Indiana State U) liases with libraries.

                Continuing communications helps connect resources and users.

Helpdesk

        Tickets received 24/7

        Mistakes are teachable/learnable moments

        

Challenges

        Managing end-user expectations

                helping users make the transition from proprietary to open-source

        Maintaining training documentation with each upgrade

        Mentoring trainers

Opportunities

        Training the trainer (Mentorship)

        Regularly scheduled user groups:

                Bookmobiles

                Reports

        Expand workshop offerings

                circulation refresher, etc.

        Expand online training.  

Laurie Davidson (Sitka, BC Libraries Cooperative)

        BCLC Support Suite:  Evergreen and Beyond

        

        Consortia

        68 libraries, 1.5 million bib records

Tools:

        Ticket Tracking System

                RT” bestpractical.com/rt

                        support.sitka.bclibraries.ca

                Each ticket establishes an automatic response, account, responsibility, and system of cues.  Manages a variety of tickets through a chain of support and system of triage.  VOIP support.

        Telephone support

                support is distributed

www.voip.ms : voicemail creates ticket.        

distinguishes between urgent and regular issues

1-800 number: 24/7 support

BCLC website (BC Library Cooperative)

http://bc.libraries.coop/

integrates support

Sitka support on website

        updated manuals

        policy, best practices

        contacts

        video

        news

        Sitka ideas

        self-serve ticketing

        

        staff client downloads

        Sitka status dashboard

                http://bc.libraries.coop/status

                up-to-the-minute status reports

        SItka Snippets

        SItka Ideas for Development

Idea torrent : Big libraries weighted more than small

Migration and Training:

        provides support on-site, on-line, and go-live.

        

        Training Schedule for Migration

                Migrate data

                90 minute pre launch

                3 hour circulation training pre-launch

                continuing online and personal support.

Evergreen Serials: Making it Work For You

Dan Wells

Anecdote of trying to use a hammer backwards.  A hammer is an effective tool, but only if you use it correctly.

Suggests alternate title:

“Bang! Bang!  Dan Well’s Serial Hammer Came Down On Their Heads!”

MFHD: Muffhead

Mard Format for Holdings

        standard for exchanging holdings data AND code.

        Basis of support is that records and code are can be interchangeable for other projects.  

        Serial MFHD are similar to MARC records

        Controlled holdings statement - Fields 853 + 863

        Free-text holdings statement - Field 866

                (his library uses for binding statement

        Groups correspond to MFHD records

        EG through MFHD record

                strings of relevant “pattern codes” translate

        Issuance = simple, uncompressed MFHD field 863

                the label is just a label

                the holding code = JSONfied Marc data

        Summaries: Generated contents collects 863s = compressed range for display

        Textual contents = simplest forms

        Building the display

                A 3 tiered abstraction

                        Actual serial -> Serial Virtual Record -> MFHD

                        [correct order?]

                SVR: normalizes and organizes data.  Simplifies logic in display code.

                Allows more back-end flexibility.  MFHD can be changed w/o changing the SVR

        Drawback: 3 layers of bugs!

                Data, MFHD code? Summary code? Display code?

                Be really specific when reporting problems!!

        MFHD v MFHD

                data can come from more than one source,

                The summary method decides which wints

                The add to  record entry is best

                        - use record entry

                        -NO NOT use

                On merging details: is similar to “Add”.  If the Pattern Code matches exactly the last 853 SRE then there won’t be a break.

        Use Cases:

                No shame in just wanting to display holdings information.  

                Wish to predict & receive issues but continue with manual holdings display entry.  Ok.. Create the record, link to corresponding distribution, set “Summary Method” to “User record entry only”

                Normal issues need predicting and receiving, but indexes and supplements will be handled manually.  Set serial control to normal.  Set Summary Method to Add or Merge

                Predict and receive, but don’t heed holding information do display (e.g. backup copies for binding)  Recommends the OPAC invisible idea, and a workaround.

Large number of copies in circulation and no namual control of holdings display

The positives are that it correlates and integrates units with content.  Probies an easy to navigate heiarchy

The drawbacks:  Does not consider Serial Record Entries or their contents.

Sidesteps SVR with customization

Challenges:  Successful integration of another crowded logic chain.

Changes in 2.4

        1.

        2. alternate serial control embedded in Serial control

Changes in the future:

        Makes no promises for 2.NExt

        MFHD will continue as the hidden basis

        Link to acquisition

        Continuity in views

        

2.Future

        

Action Triggers

Chris Sharp NOT Chris Wells

Q&A

Q: If someone has set up branch level and everyone else uses consortium level, what will happen?

A: Both trigger! 2 emails. (experience says you get none at all?)

Note: Beware of old DB entries! Could end up with emails with blank Title & Author fields

Q: What is the “environment” in the context of cloning an Action Trigger?

A: Environment gives you the parameters from original.

(As you’re doing this, remember to report bugs you come across).

Q: What would you do if you want to add a different piece to the template?

A: Fields come from fieldmapper, an XML file that maps to database tables. You could map something to the total circulation table, for example. If you are interested in adding custom text, it’s very easy.

In Search of Search

Jed Moffitt, Jeff Bond, Scott Myers & Robin Stahly

Jed:

King County Library System (KCLS)- large centralize public library system surrounding Seattle. Originally rural, not so much any more.

Agile Values

Q&A

Contributing Code to Evergreen is Easier Than You Think

Lebbeous Fogle-Weekley (Equinox Software)

Contributing happenbs in many ways

Bug Reporting

Developers don’t mean to be jerks

Tips for Good Bug Reporting

Add data to someone else’s bug to make it richer and bump it up (attention++)

More tips (thanks to Mike Peters)

Patch Testing

People skills and IT Skills

We can’t ask Jason to do it all

Not all patches call for user tests, but many do

How do we capture value from User Tests?

Patch Meetings

As with bug reports, be noisy

Code code

HTML & CSS

Javascript in Staff Client Interfaces (Ben Shum)

Technical side: Git, diff, patch and whatnot

Again, don’t be shy!

Lightning Talks

How to submit bugs using Launchpad

Bill Ott - Grand Rapids Public Library

Thinking Outside the Box

        

Envisioning Evergreen: Charting the Course to 2020

Panel discussion convened by Sharon Herbert, Kathy Lussier, Rogan Hamby, Jed Moffitt & Tara Robertson

Warning: Groups with a common cause and well-defined identity might become zealots and start wearing funny hats. Let’s stay neighborly.

Forest metaphors (PINES, SITKA, Spruce, etc.)

Where could and should EG go in the years ahead?

Jed: Wooden-finger jazz player (Thelonious Monk), some Ken Burns-type character came up to him and asked “Where is jazz going?”. He said: “I don’t know I’m just after the next gig!”


The Next Gig

Rogan: Language - Accurate & Precise

Started fixing computers because he was a reference librarian and they needed them to work

EG in 2 ways:

Integrated Library System as a term

Tara:  First job out of SLAIS@UBC, worked with EG w/ Sitka.

Conversation/Commentary: