[CODE4LIB] LAC: A Core Partner of the Open Library Environment (OLE) Project
** This message has been cross-posted to several lists ** Library and Archives Canada: A Core Partner of the Open Library Environment (OLE) Project Library and Archives Canada (LAC) is pleased to announce that it is participating in the Open Library Environment (OLE) Project joining other core partners, with Duke University as the project lead. With funding from the Andrew W. Mellon Foundation, the OLE Project will develop a design document for a next-generation open-source library automation system that fits modern expectations for library workflows and is built on a modern service-oriented architecture. This library system will be able to meet the changing and complex needs of modern libraries and library users. The small group of core partners will be highly involved in all phases of the project, by participating in all the activities, by engaging other members of the library community in planning activities and by writing the final project design document. LACs contribution will be significant and inclusive, as our mandate is to facilitate in Canada co-operation among the communities involved in the acquisition, preservation and diffusion of knowledge. Furthermore, because LAC is a national archive as well as a national library, this will bring an added perspective to the project, and will provide another opportunity to find innovative solutions to how both library and archival collections are managed and made accessible. Currently, Library and Archives Canada is engaged in a multi-year project to evergreen and modernize its own legacy library systems and incorporate them with an OAIS-compliant infrastructure to ingest, store, manage, preserve and make accessible digital holdings. LAC is embracing service-oriented architecture and Web 2.0 features as a fundamental basis for its target application architecture. By reaching out to Canadian libraries and archives, LAC has the potential to contribute significantly to both the planning and build phases of an Open Library Management System, and to bring an additional expertise and insight to the project, says Ian E. Wilson, Librarian and Archivist of Canada. We are confident that our joint efforts will lead to important national and international innovations that better meet the needs of todays researchers and users. The OLE project is a collaborative, community-based venture and offers many opportunities for individuals and organizations to participate in the project. You are invited to visit the OLE website at http://oleproject.org or to contact Gillian Cantello at [EMAIL PROTECTED] for more information regarding LACs participation in the project. Ingrid Parent Assistant Deputy Minister Documentary Heritage Collection Library and Archives Canada Zahra Pourjafar-Ziaei Deputy Chief Technology Officer Information Technology Branch Library and Archives Canada
Re: [CODE4LIB] next generation opac mailing list
On the other hand we are a bunch o' hackers, and there is more to this thing (whatever it is called) than code. We need the perspective of catalogers, reference types, administrators, vendors, etc. Thus, the idea for creating a new list. Eric, some of these folks are already here and listening. I'm not a hacker (maybe in the next life ...), but am a former cataloguer and reference techie with current responsibility for monitoring a broad range of innovative discussions, including this forum; and we all know there are vendor types on code4lib, as well. I imagine there are, in fact, enough non-coder folks here to pipe up if things start down a not-so-functional path or a path with which we might take issue. Also, I'm sure those of us here who don't code are raising code4lib points of discussion in our own workplaces and, as needed, bringing those comments back here. So, for me, here is just fine. (And I also don't want yet another list!) Cheers. Din. Donna Dinberg Systems Librarian/Analyst Services Branch Library and Archives Canada Ottawa, Ontario, Canada [EMAIL PROTECTED] ** My own comments only, not an official communication from Library and Archives Canada. **
Re: [CODE4LIB] A code4lib journal proposal
OK, folks, it's time for a comment from the peanut gallery. (Having had my 1st cuppa, I am brave.) Last night I pulled the first 3 issues of JOLA (yeah, I go back that far) from my shelf and took a look. Back in the late '60s, JOLA was reproducing images of Hollerith cards, tractor-feed print dumps, flowcharts, and formulae to illustrate some pretty detailed articles about really tech-y stuff pertaining to the mainframe environment in libraries. Compared to today's ITAL, the early JOLA was deeper into the guts of library code development. You are proposing to go back to that. I say, Yes! I like the idea of this being within the code4lib site, I like Art's idea re commenting, I like the idea of more formal sprinkled with shorter and faster. The topics are what you all have been cranking out anyway, but they will change as things move forward. Hey, you created a conference out of thin air; you can do this, and invent a new journal type in the process. (Don't forget the ISSN, please!) Although I may not know half the time what you're talking about, I scramble to keep up and enjoy every minute of it. I don't code, but perhaps I might speak for the lurking audience here that doesn't code. Incrementally, we learn every time one of you posts a new idea, or points in a different direction. We don't sit on and participate in the edge, where you are; but we are very close, and watch intently. And, we feed this stuff back into our own organizations to illuminate possibilities. Go for it! You have readership. Din. Donna Dinberg Systems Librarian/Analyst Reference and Genealogy Division Library and Archives Canada [EMAIL PROTECTED] ** My own thoughts, of course, not those of my employer. **
Re: [CODE4LIB] A code4lib journal proposal
Dorothea states elegantly what I implied (I guess I needed two cuppas): Donna's post suggests a criminally underserved population, one I think code4lib could profitably target along with its developer core: the accidental library tech. there is NOTHING out there for us. Code4lib needs to decide if its communications goals are internally or externally focused. The last statement is really important, and is compounded by what sort of publication this will be: formal/informal, peer review/not, etc. Walt Crawford's observations while reviewing the 10th anniversary edition of D-Lib Magazine in the latest _Cites_ may be useful. http://cites.boisestate.edu/civ6i4.pdf [Walt, commenting on the Bonita Wilson-Allison L. Powell article:] There's a good explanation of why D-Lib is not a refereed journal. The founders opted for quick turn-around from submission to publication over peer review... Despite its less formal status, D-Lib articles have been cited frequently, an average of nearly 118 citations per year. Perhaps, even though it's a magazine, D-Lib has enough of a journal's formality to discourage most reader feedback. [Walt, commenting on Amy Friedlander's article:] She explicitly thought and thinks of D-Lib as a magazine, not a journal. [W]e were freed from the canons of peer review to engage in speculation that might eventually feed into the formal process of juried results. So, who's your audience? How will you encourage feedback? What latitude do you want to have, and what influence do you intend? (Going to get second cup now.) Din. Donna Dinberg Systems Librarian/Analyst Reference and Genealogy Division Library and Archives Canada [EMAIL PROTECTED] ** My own thoughts, of course, not those of my employer. **
Re: [CODE4LIB] A code4lib journal proposal
Responding to Mark Jordan: but I don't think that audience should be the people you describe above (who a colleague of mine calls analogue librarians). If there are any accidental techs (or potential accidental techs) who aren't already hanging out on venues like what code4lib already is (i.e., oss4lib, /usr/lib/info, and a host of email lists, IRC channels, and tech blogs, inside and outside of library land) then they'll probably remain happy with thumbing through the existing diluted journals that librarianship is plagued with, and also remain happy with the delusion (pardon me for saying so) that they are keeping up on what's happening out in the world by reading them. There are (a whole lotta?) folks out here who don't peruse *anything* we pay attention to, but who still produce code in libraries. There are various reasons why they don't watch: no time, stuff of interest is too scattered, 1.0-level coder, etc. When I commented that those of us lurking here funnel stuff back into our (and maybe other) institutions, I was thinking specifically of funneling to those who do not watch. (Not watching is not new. Decades ago, I mentioned an article on experimental bubble memory to a senior and respected programmer; the response was basically Huh?. For those of you born after bubble memory peaked: http://www.xs4all.nl/~fjkraan/comp/pc5000/bubble.html ) This might be the value of the formal aspect of a code4lib magazine or journal. Those who do not watch blogs, websites, etc. might spend more time on something more formal when a citation is plunked under their noses. And, they may find a peer group. Din. Donna Dinberg Systems Librarian/Analyst Reference and Genealogy Division Library and Archives Canada [EMAIL PROTECTED] ** My own thoughts, of course, not those of my employer. **
