Centre of everything is the Solr index. Blacklight puts everything into Solr. Library materials is easy enough, but with Archival collections use EAD with many items (not just one item as typical of MARC).
Extended Blacklight to search EAD
index collections and single items from a collection
search results include books, entire collections, and items from collections
Digital Content
kept in Fedora – objects described using Rubys
use Hydra to manage the content in Fedora – manages RDF relationships
indexes into Solr
Need to related Fedora content to its archival collection
content originates from sources in collection, and part of series
collection metadata already exists in Solr
create RDF representations of collections
Hydra queries Solr for collection meatadata
creates objects for series, subseries, items
Issues
terrible Solr performance for series, 500+ items
no EAD “round tripping” – EAD can go into Solr, but not back out
currently 60% complete
Citation search in SOLR and second-order operators
Roman Chyla, Astrophysics Data System
Sorry, I don’t have notes for this. My brain is a bit fried by this point. Will post link when I get it.
Want to talk about communities and community building. It was a partial contextual shift as to her place in a number of communities.
Thought a lot about where she fits in. Have had a lot of identities, and thinks of herself as: nerd, geek, wonk, curator, archivist, woman, leader. Originally thought of herself as just another person, but everyone in this room should take on the role of leader.
Everything we do is part of the community, everywhere. Everyone in code4lib is part of a
community that succeeds through relationships.
Take the ethos of code4lib back to each organization.
Software Development
Every software requires a community. Each person is part of it cares. Sustaining software requires a community of people who really care. We need to think about who uses our software. This
community is not just about people who write code,
it’s also about people use the software.
The most important thing is to work with those groups of users.
Communications
These communities are built using communication, inclusiveness, consideration, even more communication, and sense of ownership.
Need to think about users, stakeholders, researchers.
Seen projects fail because they’re shared with the world but no one really takes ownership. Ownership goes both ways. Owning what you release, but also helping other projects be a success. Not everything fails, but it needs a community to thrive.
This is what we’re looking for in our communities and in our projects.
That they thrive.
You want a community that participates, looks out for each other.
What Defines a Successful Community or Project?
Participation. One project was a massive failure because no one participated.
Enthusiasm. Who would even want to fund it?
A sense of pride. ‘I’m part of that, made it happen, succeeded in part because of me.’
Learn from the history and the people who can be your mentors. Look at what you’re doing and what came before. Part of inclusiveness is acknowledging that you’re not the only person who has ever worked on the problem, who can work on the problem.
Adoption. A sign of success is that they’ve take it, use it, and contribute to it.
Now we will discuss.
Q&A Session
This supposedly not shy group, but is actually shy a lot of time.
Do we not think we’re not ‘real’ coders? Have the self imposter syndrome. But actually, she is a coder too.
Why does this community has to self-organize? Actually, awesome that this community has self-organized. Used to think every collection is unique and not doing the same thing, but we’re seeing emergence of communities that are realizing this is not true. For example, linked data community cross-fertilizing regardless of the type of collections they had. We self-organized was a sense of shared problem and shared passion.
No one organization can do it alone. We all need to work on it together.
Two most attributes to fail projects. One person thought it was a good idea, but no one else knew they were working on it. It didn’t succeed because there was no sense of participation, because no one was invited to participate. No one should work alone. We fail because we don’t collaborate.
How do you convince someone that they are a leader? Tell them that they are a success.
How do you adopt something when the leaders are not on board? ‘But everyone else is doing it, dad.’ Adoption by others. It’s really hard to be the first one though, we know.
Data-Driven Documents: Visualizing library data with D3.js
Bret Davidson, North Carolina State University Libraries
How do you measure “value” or success of projects in library setting where ROI is not measure in the amount of money?
Some Flavours of Failure
technical failure
failure to effectively address a real user need
overinvestment
outreach/promotion failure
design/UX failure
project team communication failure
failure to start
launch failure
no usage
missed opportunities (risk-averse failure)
Most of these issues boil down to a break down of communications of some sort.
What does a Project Manager Do?
Sometimes the problem is not knowing what a project manager does. The person who comes up with the idea thinks they run the project; think that they know everything to make the decisions. Or, they become the one dictating all the requirements.
A lot of the issues are political. No way to move it over to having systems oversight.
Making the Distinction?
Project manager is in charge of day to day operations. Project lead is thinking about high level requirement, more strategically, and becomes liaison between systems and the rest of the library. (e.g. public services project, would have public services librarian) Decisions are made collaboratively.
Once it settles in, make an oversight team for maintenance purposes.
The Culture of Process
Product is the reflection of the process? But, want to see evidence of process. Without ‘evidence’ of the process, what about accountability and transparency? The evidence can also be a good reference so that you don’t have to explain.
Get people to meet to discuss what they’re going to do. Can cut down a lot in the amount of time spend doing things that aren’t needed, and waiting for dependencies.
Staff frequently also think they know what users want better than users.
Islandora + digital repository initiative on campus
Sierra – ILS
EZProxy
Timeline
Islandora: lots of delays in development
ILS: had to go beta early
Option for Failure?
mission critical projects, must be salvaged
how to deal with other people’s projects failure – vendors didn’t deliver
plan for the worst before the worst happens
How to Successfully Survive a Mandated Project
practice good communication
know the political ramifications of your actions to yourself and the chain of command
work to manage expectations
be prepared to clean up any messes and make any changes
Souce: Ellern, Jill. “How to Successfully Survive a Mandated Project,” Computers in Libraries 31, no. 9 (Nov 2011): 16-20.
The Right Approach
Baby Porcupine
This is a reference to the Dilbert comic called “The Right Approach”, which a porcupine says that “we must stick them with quills – it’s the only way!”, because the ‘correct’ approach in any situation is the only approach you know.
While the project I worked on wasn’t quite like this, it was more the ‘the status quo’ is the best approach.
Need to communicate with the staff. Present and allow feedback. Need to give people an outlet to provide feedback and response to feedback. You don’t need to implement most of it.
Don’t assume that the person is ignorant, dumb, or just out to get you. You’re not always right, and sometimes ideas are tossed in just to make people think.
When a Project has Failed
Do a post-project review and go over the failure points. Post-mortem meetings can be very cathartic (even if it ends up being a rant).
Learn from your mistakes. You should always do this even if the project didn’t actually fail.
Cold
Now it’s back to braving the cold at the end of the pre-conference day.
