I started at the Society for College and University Planning in November 2010 after finishing my masters in information science from the University of Michigan in the spring. My education and professional background was, up to that point, strictly on the people side of things. Yes the library was an organization of curated information, but as far as I could see it, that information was pointless without the people connected to it (a philosophy I still believe above all). So it was a bit of a risk that SCUP took bringing me on as their metadata specialist.
SCUP is pretty self-explanatory. An affiliate of the University of Michigan’s School of Education, they’re a professional society aimed at promoting integrated planning and strategic thinking in higher education institutions. To support this vision, and to promote the resources they’ve conceived of the “cybrary.” As the name suggests, it’s a portmanteau of cyber and library. At its most basic, a digital repository for members to come and draw from a myriad of resources including SCUP’s quarterly journal, Planning for Higher Education, conference proceedings, the collected campus plans links, webcasts, etc. And while this sort of unidirectional content delivery service can be enough (users come in and query, and walk away with AN answer (maybe not the correct answer (more on that later))), it fails to encompass the scope premised in the name.
Being, as I stated before, a people-person first, and having a long history of reference and front-end patron experience in libraries, the concept of a library is for me inherently more than a collection of resources that people can access. It’s a space people can gather to exchange knowledge and collaborate. And in an organization like SCUP where your experts and professionals and knowledge holders are also your patrons, it would be remiss to not leverage their experience and their information seeking behaviors to add value and practical context for others coming into the system.
But enough with the philosophy espousing. Let’s roll the shirt sleeves up and talk practical shit.
We’re planning our initial launch for early July 2012 (yikes that’s close) to coincide with SCUP’s annual conference in Chicago. A rollout that includes some really basic functionality, and some sexy-looking web pages to get people engaged and excited. Those core functions include:
- Search
- Upload/Download
- Personal Pages
Let’s unpack this a little. The initial collection is going to be around 1,000 objects, mostly the journal articles from the past 30 years of Planning for Higher Education (a bread and butter collection to get people started). Search function is pretty self explanatory. If you can’t find anything, you really have no reason to be there (right?). The upload/download function and the personal pages are fairly tightly intertwined, and it’s how we’re going to get started with leveraging that sort of crowd-sourced knowledge base and curatorial expertise. Cybrary users will have the ability to upload notes, their own articles, etc. in a way that allows for public display to show off their knowledge and research, and in a private way allow them to have all their stuff in one spot. The personal pages will be aimed at the user collecting resources found in the cybrary and grouping them in useful ways. In the future we see this being fleshed out with notation features (think like soundcloud’s comment function but for PDFs etc), and shared collections, and a personal blog.
The project is aimed at being as cost effective as possible. To wit, it uses open source software systems and architecture, dropping the cost to only hardware and labor. The software too has vibrant communities of designers and developers providing a knowledge base for us to draw from, and real-world scenarios.
The structure of the cybrary is as follows:
- Linux Ubuntu Server (we’re using 10.04 right now because 12.04 hasn’t rolled out yet)
- Apache, PHP, Tomcat
- MySQL (we were using PostgreSQL, and will be using that for the deep archive storage,but dropped in favor of MySQL for the way it connects with wordpress and other bits and pieces)
- FEDORA Commons
- WordPress and MediaWiki (to handle the blogging, and personal pages)In the future we’re discussing adding in iRODS for handling multiple parts, connecting with SCUP’s CMS as well as preparing for potential integration w/ other institutions and associations.
Over future posts I’ll be discussing the metadata design, plans for digital curriculum and education, as well as some more nitty gritty details about searching, and how to piece all this stuff together. Thanks!