Re: [CODE4LIB] next generation opac mailing list
Eric Hellman wrote: Let's consider another function of a library catalog- resource discovery for users. Does anyone here really believe that in TEN years Google and/or competitors (maybe even mine) won't be able to hook into an inventory control system and deliver full-text, faceted, clustered, instantly relevant, translated search results out the wazoo from all the content in your library? If today's catalogs did an acceptable job of search we might be able to start a discussion. So, the argument is-- basically, very watered down-- that because the current OPACs suck, we need to abandon them, and make $global_vendor_catalog our default search entry point... which won't suck, and will also allow greater access to global resources? (and not worry our pretty little heads about it) I have always taken this problem from the other side of the equation-- (perhaps because it is the side I know I can have an effect on). Because local OPACs suck, we need to replace/improve them, not abandon them. This is part of our motivation in the Evergreen ILS project (open-ils.org). I believe we're doing a decent job, and our public and staff useability surveys back that up. I think NCSU also has the right idea. Who knows-- various vendors may come out with much-improved catalogs in response to the competition? One of our project goals is to push innovation in the larger library world. Let me be clear: I am not saying that a global catalog is not useful or shouldn't have a prominent role, but I think it should be secondary to the local, /at-fingertips collection/ and catalog (which doesn't suck). The local catalog should access the larger global resources when appropriate. We do this within our consortium-- we show the user what is immediately available on the shelf, what is up the street at the library in the next town, and then what is available throughout the state. There are going to be materials that local libraries will only want to make visible/accessible to their local users. One good example we're wrestling with here is one of our library systems has a subscription to an e-book service that only its patrons can "check out". These are the kind of materials that should only show up in that library system's "local" catalog. The uber-cat would need to know about these rules and associated boundries. (and that's just one simple example) -=-=-=-=-=-=-=- Brad LaJeunesse PINES System Administrator Georgia Public Library Service
Re: [CODE4LIB] next generation opac mailing list
On Jun 7, 2006, at 9:35 AM, Conal Tuohy wrote: As well as their MARC records, each library of the future will collect a growing variety of metadata about their holdings, lending histories, reviews contributed by users, clusters harvested from usage patterns, or from full-text transcriptions, etc, etc, all of which they will want to make use of in conjunction with other catalogue data. Hear, hear! I assert that the "catalog" is not really a "catalog" (inventory list) at all, but more like a finding aid -- a tool used to identify, acquire, and use information pertinent to the information needs and expectations of a libraries primary clientele. This tool includes stuff from a traditional catalog, but it also includes stuff not necessarily owned by libraries, such as pointers to licensed materials (increasingly journal articles), the full-text of electronic books, pre-print archives, selected materials from OAI repositories, etc. -- Eric Morgan I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
Eric Hellman wrote: > We need good global metadata catalog/registries. Which of today's > catalog functions will require a local institutional catalog tomorrow? I think this is an interesting question. My opinion is that the libraries of tomorrow will have a distributed catalogue: some of it local, some of it non-local. It makes sense to me that libraries invest in describing resources which are produced locally (i.e. as publishers, or institutional repositories), as well as in cataloguing resources which are locally appreciated in a distinct way. Institutions might just want to deal with a few facets of particular local interest, i.e. tagging resources according to some local vocabulary, and otherwise rely on other catalogues for their metadata. As well as their MARC records, each library of the future will collect a growing variety of metadata about their holdings, lending histories, reviews contributed by users, clusters harvested from usage patterns, or from full-text transcriptions, etc, etc, all of which they will want to make use of in conjunction with other catalogue data. Some of this data may be of general utility, but other data will be local in scope (and privacy laws may prohibit some data exchange in any case). These distinct information systems have to be easy to federate, efficient, and work transparently to users, so that institutions can confidently "walk on two legs"; relying on outside services for some data, while concentrating their own efforts on the areas where they can add most value to their users. Con
Re: [CODE4LIB] next generation opac mailing list
At 2:25 PM -0400 6/6/06, Teresa Victoriana Sierra wrote: Maybe you ought to sit with a reference librarian and ask why and how the catalog and OPAC are used. Are you a reference librarian who can please explain why and how today's catalog and OPAC are used, so we can think about how libraries of tomorrow can be designed to best accomplish these functions? My point is not that library catalogs are not useful things today- obviously they are. My point is that many of their functions are best accomplished in tomorrow's library without using a catalog per se. By catalog, I mean a local institutional indexed storage system containing detailed metadata records about items in a library. Let's consider one function of todays catalog- inventory control. A lot is known about inventory control systems- they're used in industry for everything from autoparts to supermarkets. It seems to me that a well designed inventory control system for tomorrows library would probably involve RFID tags- that way the library Inventory control system (LICS) could know where the books are in stead of only where they should be. Let's consider another function of a library catalog- resource discovery for users. Does anyone here really believe that in TEN years Google and/or competitors (maybe even mine) won't be able to hook into an inventory control system and deliver full-text, faceted, clustered, instantly relevant, translated search results out the wazoo from all the content in your library? If today's catalogs did an acceptable job of search we might be able to start a discussion. We need good global metadata catalog/registries. Which of today's catalog functions will require a local institutional catalog tomorrow? -- Eric Hellman, DirectorOCLC Openly Informatics Division [EMAIL PROTECTED]2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://www.openly.com/1cate/ 1 Click Access To Everything
Re: [CODE4LIB] next generation opac mailing list
> That by trotting out their Endeca powered catalog, they've finally > gotten the tangible that we nerds have been unable to get > institutional support for. Now every librarian in the country wants > clustering and faceted search. Ah, and look how they did it. To paraphrase an olde-tyme Internet expression, they declared their vendor an obstacle and routed around it. For years they had said "the OPAC sucks." But targeting ILS vendors wasn't effective. Not enough people in LibraryLand care. What was the incentive for a vendor to change over the occasional scattered peeping of a few nerds? So they layered a faceted search engine on top of an existing product. In doing so, they incidentally demonstrated the "missing module" of the library catalog--user navigation. Not sure every librarian wants clustering and faceted search, but one can only hope. Btw, for you grow-your-own types, do check out Flamenco, open source faceting software. Flamenco + indexer + stemmer + spell check + some homebrewed SLA tool might equal a pretty nice search engine to compensate for YOUR missing module. Strategery--catch the fever! Karen G. Schneider [EMAIL PROTECTED]
Re: [CODE4LIB] next generation opac mailing list
Hiya, On 6/7/06, Ross Singer <[EMAIL PROTECTED]> wrote: That by trotting out their Endeca powered catalog, they've finally gotten the tangible that we nerds have been unable to get institutional support for. Now every librarian in the country wants clustering and faceted search. Sorry, I'm in the wrong country. :) In fact, that event as much as it triggered peoples hearts and minds, it never shook the foundation of the OPAC in this place. But this time last year, I defy you to tell me that you could have trotted out a project like that to anybody outside the systems office (that wasn't already labelled a 'systems apologist'). Possibly not. Hmm. No, not with the OPAC, but other systems. I think libraries have put too much faith in vendors who create crappy systems and continues to do so. If vendors want libraries to buy their stuff, they need to make sure they've got good stuff; it's getting easier and easier to do these things ourselves. Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
On 6/6/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote: Hi, > You can thank NCSU for bringing the catalogers, reference types, > administrators, vendors, etc. to the table. Hmm, how so? I've been at the table with many of them for many years already and know them quite well. :) Are you referring to something specific? That by trotting out their Endeca powered catalog, they've finally gotten the tangible that we nerds have been unable to get institutional support for. Now every librarian in the country wants clustering and faceted search. But this time last year, I defy you to tell me that you could have trotted out a project like that to anybody outside the systems office (that wasn't already labelled a 'systems apologist'). -Ross. Regards, Alexander -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
Hi, On 6/7/06, Jonathan Rochkind <[EMAIL PROTECTED]> wrote: My impression is that there are LOTS of catalogers interested in discussing this topic---the future of The Catalog. As much as I would love to disagree with you, I don't. :) My stance on this is not to let hackers create applications as they see fit, dear Dog, no! I'm a die-hard user-centred design and usability guy; my life is dedicated to develop solutions fit for the user, wheter that be patrons, catalogers, super-users and otherwise. I'm more talking about politics of *actually* doing something; I find it easy to talk about innovation with my collegues, but hard to do in practice, although we're setting up a "labs" area these days in an attempt to break free of the tyranny of PRINCE2 and top-down hiearchies. But hey, i realise this is probably besides the point; if we have fruitful discussions, maybe someone can do something with it. Some coders seem to assume that the cataloging community doesn't realize the need for change, or doesn't understand the possibilities of the online catalog. I think this is more and more NOT the case. Catalogers too realize that things are broken, change is the topic of discussion. Actually, I've found the reverse to be true; catalogers overly aware of things being broken, but having hackers that either can't see the problem or are too busy to do so. My feeling about this all is that we're too busy maintaining the MARC Legacy than create a shining new one which may or may not solve the problem. Of course, the problem with MARC is the culture not the technology, so in order to change the culture we need a *whopping* effort put in by *all* libraries around the world. No very likely, but it would be fantastic if we could. But such common vision is desperately needed. I'd say such common vision is desperately needed on the management level! What drives the libraries if not management? Sure, footsoldiers and captains can push the envelope, but only so far before it becomes political, huge, convuluted, a project with a steering commitee, and so forth. For me the strategy is to create prototypes to demonstrate what we're on about, and in my case I do that *with* catalogers, reference librarians and other friends around the library / library world. The idea here is to unite the bottom soldiers in such a way that the top management can see the light and resource and process accordingly. So we desperately need more forums for discussion involving both catalogers and developers, focused on this topic. No, we desperately need everyone to join the same forums! Not more forums, but less! Less is more. We don't need yet another commitee; we need one stronger one. But hey, I'm dreaming. As Eric writes, an important topic for discussion is: "To what degree should traditional cataloging practices be used in such a thing, or to what degree should new and upcoming practices such as FRBR be exploited?" The danger here is that automated processes adds a quality check to our processes, and a lot of people don't like that, especially top management, because it points out mistakes made in the past. Technically we don't have many problems, we can do pretty much anything we'd like to do if we really wanted to, but it's all about internal politics and shuffeling of resources which decides wheter it should be done or not. If *management* don't understand what hackers and catalogers and reference librarians are talking about, we're stuffed! Anyway, I don't think we disagree on this, only the part about needed yet another mailing-list. Regards, Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
In our effort to redefine the future, it is important that we all challenge our assumptions. We should cherish our heretics, right or wrong. My $.02 is that we don't need yet another system; we need to develop and adopt standards and coerce everyone in sight to play along. Standards enable innovation. Systems deter it. Jeff > -Original Message- > From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of > Teresa Victoriana Sierra > Sent: Tuesday, June 06, 2006 2:25 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] next generation opac mailing list > > I generally don't get into the discussion threads, but merely enjoy what > is being said. However, Eric...you have touched a nerve. I agree that we > need to be thinking about the way libraries will look in the future. But > to say that the library catalog is serving only the purposes of the people > who fund them and feed on their vanity, is pretty strong and misguided. > Maybe you ought to sit with a reference librarian and ask why and how the > catalog and OPAC are used. > > > > Teri Sierra, Chief > Serial and Government Publications Division > Library of Congress > 202-707-5277 > 202-707-6128 (fax) > > >>> [EMAIL PROTECTED] 06/05/06 8:50 PM >>> > I would argue that our energy would be better spent thinking about > the next generation library rather than the next generation opac. > > Is it just me, or does anyone else feel that the very idea of having > a catalog as an important component of a library smacks of retrograde > thinking? To my mind, in a clean-slate NG Library architecture, the > library catalog should only exist as a facade that recognizes of the > vanity of libraries and the people who fund them. > > I can think of no technical justification for library catalogs as we > look forward. If not the next generation, then the next-next > generation of libraries. The functions that exist today in library > catalogs need to be pushed in two directions- toward the user on one > hand, and towards global registries on the other. > > the other Eric > -- > > Eric Hellman, DirectorOCLC Openly > Informatics Division > [EMAIL PROTECTED]2 Broad St., Suite 208 > tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 > http://www.openly.com/1cate/ 1 Click Access To Everything
Re: [CODE4LIB] next generation opac mailing list
I generally don't get into the discussion threads, but merely enjoy what is being said. However, Eric...you have touched a nerve. I agree that we need to be thinking about the way libraries will look in the future. But to say that the library catalog is serving only the purposes of the people who fund them and feed on their vanity, is pretty strong and misguided. Maybe you ought to sit with a reference librarian and ask why and how the catalog and OPAC are used. Teri Sierra, Chief Serial and Government Publications Division Library of Congress 202-707-5277 202-707-6128 (fax) >>> [EMAIL PROTECTED] 06/05/06 8:50 PM >>> I would argue that our energy would be better spent thinking about the next generation library rather than the next generation opac. Is it just me, or does anyone else feel that the very idea of having a catalog as an important component of a library smacks of retrograde thinking? To my mind, in a clean-slate NG Library architecture, the library catalog should only exist as a facade that recognizes of the vanity of libraries and the people who fund them. I can think of no technical justification for library catalogs as we look forward. If not the next generation, then the next-next generation of libraries. The functions that exist today in library catalogs need to be pushed in two directions- toward the user on one hand, and towards global registries on the other. the other Eric -- Eric Hellman, DirectorOCLC Openly Informatics Division [EMAIL PROTECTED]2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://www.openly.com/1cate/ 1 Click Access To Everything
Re: [CODE4LIB] next generation opac mailing list
nucat4lib ? hepcat4lib ? nopac4lib ? andrew p.s. happy national day of slayer, http://www.nationaldayofslayer.org/
Re: [CODE4LIB] next generation opac mailing list
I'd be happy to include the info on Catalogablog. Thanks again to everyone who gave me help with that OAI file. Sincerely, David Bigwood Catalogalog http://catalogablog.blogspot.com -Original Message- From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of Jason Etheridge Sent: Tuesday, June 06, 2006 10:47 AM To: CODE4LIB@listserv.nd.edu Subject: Re: [CODE4LIB] next generation opac mailing list > My impression is that there are LOTS of catalogers interested in > discussing this topic---the future of The Catalog. One of our catalogers suggested that once we do have a new list, that we publish details on AUTOCAT and OCLCCAT. -- Jason Etheridge GPLS -- PINES Development http://open-ils.org/
Re: [CODE4LIB] next generation opac mailing list
> My impression is that there are LOTS of catalogers interested in > discussing this topic---the future of The Catalog. (I think there's > no reason to stop calling it the catalog, although 'OPAC' as an > acronym is probably best abandoned). Some coders seem to assume > that the cataloging community doesn't realize the need for change, or > doesn't understand the possibilities of the online catalog. I think > this is more and more NOT the case. Catalogers too realize that > things are broken, change is the topic of discussion. I second this heartily. I am not a cataloger, but when I wade into the topic of catalogs, I am impressed by the responses, sometimes visionary, sometimes apocalyptic, from catalogers who are grappling with these issues. I work with a tremendously gifted cataloger who has that valued dual vision. > possibilities. But what's also true is, yes, there's a lot of > dispute about what is to be done. (I also think that what is to be > done is not necessarily clear; while there are some things I > personally think are clear that many colleagues irrationally [ :) ] > disagree on, the terrain in general is in fact a lot less clear than > some coders may think, in my opinion.) All true on these points, and LibraryLand does not need (and more to the point, will not adopt) solutions crafted solely by the coders. I am not a coder or a cataloger and with great fear and trembling I have waded into the catalog discussion because I felt it was important. Fortunately if I have been mocked it has been behind my back ;> . Even with my toe-in-the-water ruminations, I am conflicted with my own admittedly preliminary and only partially formed conclusions, and on alternate days am equally persuaded by other models. What is the best design-the One True Catalog or A Million Points of Catalog? Are there other models? If we do one does that mean opting for total dominion by a major company, I mean nonprofit? If we do the other are we stuck in the system design of the 1960s? > created by coders? Will the coders and the catalogers be able to > communicate... If you really want a discussion on this topic, the best argument for establishing another list is the naming issue, and the second is a question of list dominion. I am not a coder; I'm not a cataloger. But I know a few things, and I've worked or do work with coders, catalogers, reference, etc. I felt extremely anxious posting at all about indexing software and the qualities of good search last week, even though I've spent the last year developing and evaluating software against standards for search and have some passionate and I'd like to think well-informed ideas on the issue. A broader group devoted to the topic of "catalog" is less likely to do the coder take-down that can sometimes happen when coders get distracted by the technological imprecision of the non-coder's ideas and more likely to listen to what people like me are trying to say. , do they speak enough of the same language, do they have > enough of the same conceptual model of what we're talking about, > enough of the same ideas of where we should be going? I don't know. > But such common vision is desperately needed. It's possible when this discussion gets broadened that the coders are given cause to evaluate and refine their notion of the "ideas of where we should be going." In any event it would be richer as a collective discussion. > As Eric writes, an important topic for discussion is: "To what degree > should traditional cataloging practices be used in such a thing, or > to what degree should new and upcoming practices such as FRBR be > exploited?" Coders can't have this discussion without catalogers if > it's not just going to be a fantasy discussion. And we should be > humble enough to realize that we may not in fact even understand the > question as well as (some) catalogers, and the cataloging community > in fact has an awful lot to contribute. Yes, on all points, if cataloger is understood as a term that means "other than coder" (and let's not forget FAST-and I wish there were more discussion about FAST widely in the community because it FASTinates me but I'm not able to attend that one ALA program I am pointed to whenever I seek more information about it). You aren't going to get oodles of directors or reference folk or whatnot on a list like this, at least not participating. But if the discussion is forced to be at, um, higher than machine level, you might get wide viewing from the peanut gallery, who will pingpong ideas around the bibliogalaxy. (Er... how easy is it to view the archives of this list? I had an embarrassingly tough time getting on this list, and no memory of other details about it.) I would also suggest that statements such as MARC Must Die-which I do not disagree with-might best be posed as questions: What's Wrong With MARC? For one thing, it would make assumptions difficult. For another, it suggests that the list subscribers are being invited to a
Re: [CODE4LIB] next generation opac mailing list
My impression is that there are LOTS of catalogers interested in discussing this topic---the future of The Catalog. One of our catalogers suggested that once we do have a new list, that we publish details on AUTOCAT and OCLCCAT. -- Jason Etheridge GPLS -- PINES Development http://open-ils.org/
Re: [CODE4LIB] next generation opac mailing list
On Tue, 6 Jun 2006, Michael J. Giarlo wrote: On 6/5/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote: Oh, this one is easy to answer; we need to get away from MARC. No, not the content of MARC, nor the idea of it, nor necessarily even the MARC format and standard itself, but we need to get away from "we need MARC" and the idea that knowledge sharing in libraries are best done through MARC and that Z39.50 must be part of our requirements. Lib Tek: The Next Generation -- The Wrath of MARC. Is it too geeky to point out that The Warth of MARC would be more properly associated with Lib Tek, the original? You'd need something like Lib Tek: The Next Generation -- MARC-Nemsis (If we allow adaptation of episode titles maybe something like MARC-pid. Thanks to Wikipedia for being an ever useful source of pop culture.) Jon Gorman
Re: [CODE4LIB] next generation opac mailing list
At 10:34 AM +1000 6/6/06, Alexander Johannesen wrote: On 6/6/06, Eric Lease Morgan <[EMAIL PROTECTED]> wrote: 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. Ok, that's fair enough, but will they come? My experiences with these kind of things is that what we would like to see happen won't. Maybe I'm overly pessimistic, but I think there is far too much politics in the library world these days for real discussions to take place My impression is that there are LOTS of catalogers interested in discussing this topic---the future of The Catalog. (I think there's no reason to stop calling it the catalog, although 'OPAC' as an acronym is probably best abandoned). Some coders seem to assume that the cataloging community doesn't realize the need for change, or doesn't understand the possibilities of the online catalog. I think this is more and more NOT the case. Catalogers too realize that things are broken, change is the topic of discussion. More and more catalogers have a grasp of the possibilities of computer retrieval too, and the need to fix cataloging practice to fulfill those possibilities. But what's also true is, yes, there's a lot of dispute about what is to be done. (I also think that what is to be done is not necessarily clear; while there are some things I personally think are clear that many colleagues irrationally [ :) ] disagree on, the terrain in general is in fact a lot less clear than some coders may think, in my opinion.) So discussion of change is afoot. Will catalogers subscribe to a list created by coders? Will the coders and the catalogers be able to communicate, do they speak enough of the same language, do they have enough of the same conceptual model of what we're talking about, enough of the same ideas of where we should be going? I don't know. But such common vision is desperately needed. So we desperately need more forums for discussion involving both catalogers and developers, focused on this topic. All kinds of catalogers (dealing with various materials, and various audiences; and perhaps too metadata practicioners on the edges of the library community as well), and all kinds of developers (commercial, open source, institutional). In person (ALA?), online, through scholarly publication and interaction from both communities, all of that. Very much needed. To successfully do that might require some networking and politicking with the right people though, yeah, not just creating a mailing list among ourselves. And it will surely be a struggle to develop a common language and vision, yes. As Eric writes, an important topic for discussion is: "To what degree should traditional cataloging practices be used in such a thing, or to what degree should new and upcoming practices such as FRBR be exploited?" Coders can't have this discussion without catalogers if it's not just going to be a fantasy discussion. And we should be humble enough to realize that we may not in fact even understand the question as well as (some) catalogers, and the cataloging community in fact has an awful lot to contribute. --Jonathan
Re: [CODE4LIB] next generation opac mailing list
On 6/5/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote: Oh, this one is easy to answer; we need to get away from MARC. No, not the content of MARC, nor the idea of it, nor necessarily even the MARC format and standard itself, but we need to get away from "we need MARC" and the idea that knowledge sharing in libraries are best done through MARC and that Z39.50 must be part of our requirements. Lib Tek: The Next Generation -- The Wrath of MARC. -Mike
Re: [CODE4LIB] next generation opac mailing list
On Jun 6, 2006, at 10:54 AM, Dinberg Donna wrote: 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. Noted, but most people here on code4lib are hackers. The idea of a library catalog needs to reach a much wider audience. That is why I advocate a new list. -- Eric Lease Morgan University Libraries of Notre Dame I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
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] next generation opac mailing list
>The catalog is going to be with us in one form or another. One thing that >never ceases to amaze me is how the library field is sooo quick to throw >overboard useful tools just for the sake of something different. The ILS >in its present form has LOTS of room for improvement but it doesn't mean we >have to hide it behind other labels or have to turn it into some nebulous >concept that doesn't mean anything. One might not necessarily mean throwing out the other. If you go to Chapters here in Canada (like Barnes & Noble in the States), you will see a web interface that is a totally separate system from the inventory application that manages the collection, and round-trips between them for the status of an item (and you occasionally see staff looking at the green screens for the inventory functions). I think a next generation opac is more likely to be something that exists in multiple forms, and has some smart strategies for synchronization and maximizing what each system does best. I would like to see an instance of the catalogue maintained as a lucene index for mixing and matching with other lucene indexes for example (think "find me everything in X that I have rights to because of Y" or "everything in X that is not in Y"), another version that could be consumed by desktop indexers, yet another for handing out on a USB drive as a portable app (you could probably do this with lucene now or any other indexing system with decent compression), and so on. Most of all, I want a version that does some sort of type-ahead in a search box on the top of every web page without venturing into a separate interface at all, and one that can inject itself into arbitrary web spaces where desired content is identified in order to sort out rights management issues. But I am not sure that the equivalent of a green screen for inventory control isn't going to be running somewhere behind all of this, I just hope our patrons never have to know it's there. art
Re: [CODE4LIB] next generation opac mailing list
I am forwarding this message because, for some reason, it came to me as the administrator of the list. Hmmm... Hi, Longtime reader, firsttime submitter. I am a cataloger who has been working with digitizing, PHP, MySQL and trying to move the catalog out of the ILS. I think that this forum is the correct one for these discussions. To me CODE4LIB means that we are working to develop real solutions for real problems that the vendors will not be able to do because of financial and contractual restraints. I also believe that there are going to be multiple solutions that work -- even multiple solutions at single institutions. I don't think that there is a real weakness with MARC, but there is with the ways that it has been used to date. I really appreciate the "crappyblackboxiethingy". Our real problem is not the rich information that has been created over the last 100 years, but the fact that I can only get to it if I use a special tool. Seeing as Dublin Core et al. have been based to a great extent on MARC and AACR, it is a shame (and as a cataloger, may I say embarassment) that MARC itself is so lacking in interoperability. I believe that that is the key: interoperability. I believe that we need to work towards means of integrating the "catalog" with the rest of the information world. OpenWorldCat is a great step in this direction, but now we need to get our catalogers and other librarians and users adding "metadata" (aka "cataloging," "tagging", "taxonomies", "reviews", etc.) to the rest of the materials. We have the basic tools available to start doing this, especially the open source tools for converting MARC to MARCXML and Lucene, Z39.50, etc. I am really excited by the work that the CODE4LIB people have already been doing. I'll stop for now. Sorry I've been so longwinded, Ross Hi, On 6/6/06, Eric Lease Morgan <[EMAIL PROTECTED]> wrote: 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. Ok, that's fair enough, but will they come? My experiences with these kind of things is that what we would like to see happen won't. Maybe I'm overly pessimistic, but I think there is far too much politics in the library world these days for real discussions to take place outside of the hacking realm. Hmm. Maybe I should get soome coffee and come back and answer things in a more positive light. :) Regards, Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __ -- Ross Shanley-Roberts Authority Control Librarian/ Special Projects Cataloger Miami University Oxford, OH 45056 513 529-3376 -- Eric
Re: [CODE4LIB] next generation opac mailing list
Hello, I'm a noobie to Code4Lib... hi, everyone. I think OPACs are actually very good at keeping track of the older information structures (i.e. print serials). I would have no problem with abandoning the OPAC (whether entirely or conceptually as new versions are made) from a certain point forward, and using a new system that accomodates new information types (blogs? electronic journals, etc) and implements new features whether or not they are retrospective-ly capable. Looking at the E-R diagram for Endeavor's OPAC was kinda what convinced me not to get too eager to dump the old school OPAC. Jody Original message >Date: Tue, 6 Jun 2006 00:09:54 -0400 >From: Ross Singer <[EMAIL PROTECTED]> >Subject: Re: [CODE4LIB] next generation opac mailing list >To: CODE4LIB@listserv.nd.edu > >Eric, > >But that's where all my stuff is! > >-Ross. > >On 6/5/06, Eric Hellman <[EMAIL PROTECTED]> wrote: >> I would argue that our energy would be better spent thinking about >> the next generation library rather than the next generation opac. >> >> Is it just me, or does anyone else feel that the very idea of having >> a catalog as an important component of a library smacks of retrograde >> thinking? To my mind, in a clean-slate NG Library architecture, the >> library catalog should only exist as a facade that recognizes of the >> vanity of libraries and the people who fund them. >> >> I can think of no technical justification for library catalogs as we >> look forward. If not the next generation, then the next- next >> generation of libraries. The functions that exist today in library >> catalogs need to be pushed in two directions- toward the user on one >> hand, and towards global registries on the other. >> >> the other Eric >> -- >> >> Eric Hellman, DirectorOCLC Openly >> Informatics Division >> [EMAIL PROTECTED]2 Broad St., Suite 208 >> tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 >> http://www.openly.com/1cate/ 1 Click Access To Everything >> >>
Re: [CODE4LIB] next generation opac mailing list
Hi, You can thank NCSU for bringing the catalogers, reference types, administrators, vendors, etc. to the table. Hmm, how so? I've been at the table with many of them for many years already and know them quite well. :) Are you referring to something specific? Regards, Alexander -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
Eric, But that's where all my stuff is! -Ross. On 6/5/06, Eric Hellman <[EMAIL PROTECTED]> wrote: I would argue that our energy would be better spent thinking about the next generation library rather than the next generation opac. Is it just me, or does anyone else feel that the very idea of having a catalog as an important component of a library smacks of retrograde thinking? To my mind, in a clean-slate NG Library architecture, the library catalog should only exist as a facade that recognizes of the vanity of libraries and the people who fund them. I can think of no technical justification for library catalogs as we look forward. If not the next generation, then the next-next generation of libraries. The functions that exist today in library catalogs need to be pushed in two directions- toward the user on one hand, and towards global registries on the other. the other Eric -- Eric Hellman, DirectorOCLC Openly Informatics Division [EMAIL PROTECTED]2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://www.openly.com/1cate/ 1 Click Access To Everything
Re: [CODE4LIB] next generation opac mailing list
Alex, You can thank NCSU for bringing the catalogers, reference types, administrators, vendors, etc. to the table. -Ross. On 6/5/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote: Hi, On 6/6/06, Eric Lease Morgan <[EMAIL PROTECTED]> wrote: > 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. Ok, that's fair enough, but will they come? My experiences with these kind of things is that what we would like to see happen won't. Maybe I'm overly pessimistic, but I think there is far too much politics in the library world these days for real discussions to take place outside of the hacking realm. Hmm. Maybe I should get soome coffee and come back and answer things in a more positive light. :) Regards, Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
On 6/6/06, Michael Bowden <[EMAIL PROTECTED]> wrote: We need something. My ILS has decided that their next generation catalog will be a portal with its own database, etc. I already have one database with MARC data why do I need another to hold the non-MARC data. Why isn't my ILS working to expand/create the next generation MARC record? I think the next generation catalog goes hand and hand with the next generation of MARC. Oh, this one is easy to answer; we need to get away from MARC. No, not the content of MARC, nor the idea of it, nor necessarily even the MARC format and standard itself, but we need to get away from "we need MARC" and the idea that knowledge sharing in libraries are best done through MARC and that Z39.50 must be part of our requirements. For example, MARC can hold some change control info, but never to the granulaity that supports for example an NBD which can properly update records and work on a distributed model. But as soon as we put that info outside of MARC, the culture will choose to ignore the problem rather than try to change it. The *culture* of MARC is the problem. I don't think the OPAC will go away, nor that it absolutely must, but the very idea of an OPAC is based on knowing what our patrons want; books that we've cataloged. But all too often we have no idea what they want; all we've got are assumptions. I think we've come a long way, but the time to look anew to what purpose the OPAC serves certainly is ripe. Ok, I'll stop now. :) Regards, Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
I think this makes perfect sense. We need this forum. The catalog is going to be with us in one form or another. One thing that never ceases to amaze me is how the library field is sooo quick to throw overboard useful tools just for the sake of something different. The ILS in its present form has LOTS of room for improvement but it doesn't mean we have to hide it behind other labels or have to turn it into some nebulous concept that doesn't mean anything. Why do librarians instinctively run away from their purpose? I've worked all over the place in the library world and I work in a public library now. Here on Mount Olympus we spend so much time arguing pendantically about MARC-this and Z39.50-that, and fretting and worrying about what OCLC is up to. All the while our patrons are coming up to the OPAC search stations and using the all too limiting user interface we present them to type in the one or two keywords that they know in order to find something in the library. Do they care about all what we talk about? No!!! They just want to find their book or resource in whatever form it is in, get it, and go on with their lives. The catalog is one of the the main interfaces to the library that all patrons use. How can we make that experience most productive? We need to pay lot of attention to that. Peter Schlumpf -Original Message- >From: Michael Bowden <[EMAIL PROTECTED]> >Sent: Jun 5, 2006 9:04 PM >To: CODE4LIB@listserv.nd.edu >Subject: Re: [CODE4LIB] next generation opac mailing list > >I have been reading the comments here and I am in favor of creating a >list for discussing the next generation catalog/information >system/whatever. I have been to 2 workshops in the last month where I >have heard 2 people from different universities talk about OCLC being >*THE* interface to the library catalog in the future -- truly a >WorldCat. I consider myself open to new ideas but this one really >worries me. And when you look at OCLCs long range plans, they want to >become *THE* library interface. > >We need something. My ILS has decided that their next generation >catalog will be a portal with its own database, etc. I already have one >database with MARC data why do I need another to hold the non-MARC data. > Why isn't my ILS working to expand/create the next generation MARC >record? I think the next generation catalog goes hand and hand with the >next generation of MARC. > >-- >Michael Bowden >Harrisburg Area Community College > > > >>>> [EMAIL PROTECTED] 6/5/2006 8:17:07 PM >>> > >On Jun 5, 2006, at 7:33 PM, Alexander Johannesen wrote: > >> What's wrong with keeping such discussions to this very list? It's >> very on-topic, and I'm not sure I need yet another list (I think I'm >> up to around 30-something now!). > > >I understand this sentiment. Really! > >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 Lease Morgan >University Libraries of Notre Dame > >I'm hiring a Senior Programmer Analyst. >See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
I have been reading the comments here and I am in favor of creating a list for discussing the next generation catalog/information system/whatever. I have been to 2 workshops in the last month where I have heard 2 people from different universities talk about OCLC being *THE* interface to the library catalog in the future -- truly a WorldCat. I consider myself open to new ideas but this one really worries me. And when you look at OCLCs long range plans, they want to become *THE* library interface. We need something. My ILS has decided that their next generation catalog will be a portal with its own database, etc. I already have one database with MARC data why do I need another to hold the non-MARC data. Why isn't my ILS working to expand/create the next generation MARC record? I think the next generation catalog goes hand and hand with the next generation of MARC. -- Michael Bowden Harrisburg Area Community College >>> [EMAIL PROTECTED] 6/5/2006 8:17:07 PM >>> On Jun 5, 2006, at 7:33 PM, Alexander Johannesen wrote: > What's wrong with keeping such discussions to this very list? It's > very on-topic, and I'm not sure I need yet another list (I think I'm > up to around 30-something now!). I understand this sentiment. Really! 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 Lease Morgan University Libraries of Notre Dame I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
I would argue that our energy would be better spent thinking about the next generation library rather than the next generation opac. Is it just me, or does anyone else feel that the very idea of having a catalog as an important component of a library smacks of retrograde thinking? To my mind, in a clean-slate NG Library architecture, the library catalog should only exist as a facade that recognizes of the vanity of libraries and the people who fund them. I can think of no technical justification for library catalogs as we look forward. If not the next generation, then the next-next generation of libraries. The functions that exist today in library catalogs need to be pushed in two directions- toward the user on one hand, and towards global registries on the other. the other Eric -- Eric Hellman, DirectorOCLC Openly Informatics Division [EMAIL PROTECTED]2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://www.openly.com/1cate/ 1 Click Access To Everything
Re: [CODE4LIB] next generation opac mailing list
Hi, On 6/6/06, Eric Lease Morgan <[EMAIL PROTECTED]> wrote: 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. Ok, that's fair enough, but will they come? My experiences with these kind of things is that what we would like to see happen won't. Maybe I'm overly pessimistic, but I think there is far too much politics in the library world these days for real discussions to take place outside of the hacking realm. Hmm. Maybe I should get soome coffee and come back and answer things in a more positive light. :) Regards, Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
On Jun 5, 2006, at 7:33 PM, Alexander Johannesen wrote: What's wrong with keeping such discussions to this very list? It's very on-topic, and I'm not sure I need yet another list (I think I'm up to around 30-something now!). I understand this sentiment. Really! 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 Lease Morgan University Libraries of Notre Dame I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
+1 (please) --Brad Alexander Johannesen wrote: What's wrong with keeping such discussions to this very list? It's very on-topic, and I'm not sure I need yet another list (I think I'm up to around 30-something now!). Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
On Jun 5, 2006, at 7:33 PM, Alexander Johannesen wrote: What's wrong with keeping such discussions to this very list? It's very on-topic, and I'm not sure I need yet another list (I think I'm up to around 30-something now!). Here? Here! Hear, hear!
Re: [CODE4LIB] next generation opac mailing list
What's wrong with keeping such discussions to this very list? It's very on-topic, and I'm not sure I need yet another list (I think I'm up to around 30-something now!). Alex -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __
Re: [CODE4LIB] next generation opac mailing list
Whatever you want to call these things I would definitely subscribe to this list. Thought I do agree with Karen that catalog is what we are talking about, regardless of what label we decide to put on it. Peter Schlumpf -Original Message- >From: Ross Singer <[EMAIL PROTECTED]> >Sent: Jun 5, 2006 5:13 PM >To: CODE4LIB@listserv.nd.edu >Subject: Re: [CODE4LIB] next generation opac mailing list > >I would definitely subscribe if it was called >bigcrappyblackboxesthatcostanarmandaleg-l, but I'd never post to it >because I'd keep misspelling it. > >That could be good or bad. > >-Ross. > >On 6/5/06, Michael J. Giarlo <[EMAIL PROTECTED]> wrote: >> I'd also be interested. As a linguist, I remain name-agnostic. You could >> call it bigcrappyblackboxesthatcostanarmandaleg-list and I would still >> subscribe. >> >> -Mike >> >>
Re: [CODE4LIB] next generation opac mailing list
Nextgencat4lib? kgs
Re: [CODE4LIB] next generation opac mailing list
As a technical person (library guy, but not a librarian!), I agree with Karen in including 'catalog' in the list name. I think, this helps support people to understand what this list is about. Just for a thought.. ngcatalog4web? May be it is wordy too . BTW ngo in ngo4lib could mean "non-gazetted officers" in some counties esp. in India Vishwam Vishwam Annam Web Developer Wright State University Libraries Dayton, OH 45435 K.G. Schneider wrote: I agree -- the term OPAC brings with it a whole set of last-generation assumptions. It strikes me as being like starting a list on new developments in Web technology called "Gopher 3.0" or something. Also, NGO is traditionally used to describe Non-Governmental Organizations like the Red Cross, Amnesty International, etc. Probably more people are familiar with the acronym NGO than with OPAC. --Casey As a word person, I keep circling back to the word "catalog," because... * It's not an acronym-particularly not an acronym that makes my skin crawl; it's nice plain English * It is broad enough to refer to all the functions a catalog might include: user interface (which is what OPAC refers to), commerce, inventory, reporting, data management... Just a thought. Karen S.
Re: [CODE4LIB] next generation opac mailing list
On Jun 5, 2006, at 6:26 PM, K.G. Schneider wrote: Hmmm, but the objective is not bigcrappyblackboxesthatcostanarmandaleg... Maybe it should be nirvana-l, or neplusultra-l, or nextyearinjerusalem-l ;) Seriously, I'm leaning towards nglc4lib, next generation library catalogs for libraries. -- Eric Morgan University Libraries of Notre Dame I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
> I would definitely subscribe if it was called > bigcrappyblackboxesthatcostanarmandaleg-l, but I'd never post to it > because I'd keep misspelling it. > > That could be good or bad. > > -Ross. Hmmm, but the objective is not bigcrappyblackboxesthatcostanarmandaleg... Maybe it should be nirvana-l, or neplusultra-l, or nextyearinjerusalem-l ;) Karen S.
Re: [CODE4LIB] next generation opac mailing list
I would definitely subscribe if it was called bigcrappyblackboxesthatcostanarmandaleg-l, but I'd never post to it because I'd keep misspelling it. That could be good or bad. -Ross. On 6/5/06, Michael J. Giarlo <[EMAIL PROTECTED]> wrote: I'd also be interested. As a linguist, I remain name-agnostic. You could call it bigcrappyblackboxesthatcostanarmandaleg-list and I would still subscribe. -Mike
Re: [CODE4LIB] next generation opac mailing list
I'd also be interested. As a linguist, I remain name-agnostic. You could call it bigcrappyblackboxesthatcostanarmandaleg-list and I would still subscribe. -Mike
Re: [CODE4LIB] next generation opac mailing list
> I agree -- the term OPAC brings with it a whole set of last-generation > assumptions. It strikes me as being like starting a list on new > developments in Web technology called "Gopher 3.0" or something. > > Also, NGO is traditionally used to describe Non-Governmental > Organizations like the Red Cross, Amnesty International, etc. Probably > more people are familiar with the acronym NGO than with OPAC. > > --Casey As a word person, I keep circling back to the word "catalog," because... * It's not an acronym-particularly not an acronym that makes my skin crawl; it's nice plain English * It is broad enough to refer to all the functions a catalog might include: user interface (which is what OPAC refers to), commerce, inventory, reporting, data management... Just a thought. Karen S.
Re: [CODE4LIB] next generation opac mailing list
I agree -- the term OPAC brings with it a whole set of last-generation assumptions. It strikes me as being like starting a list on new developments in Web technology called "Gopher 3.0" or something. Also, NGO is traditionally used to describe Non-Governmental Organizations like the Red Cross, Amnesty International, etc. Probably more people are familiar with the acronym NGO than with OPAC. --Casey >>> [EMAIL PROTECTED] 06/05/06 12:54 PM >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Perhaps I'm too much of a radical, but for me even leaving "OPAC" in the mailing list name would be to already admit defeat. Peter On 6/5/06 3:40 PM, Eric Lease Morgan wrote: > What do y'all think of the possible creation of a mailing list called > "next generation" OPAC for libraries -- ngo4lib? > > The purpose of such a list would be to discuss things like but not > limited to: > >* who would be the audience of such a system >* what such a system might contain >* how such a system would be created - -- Peter Murray http://www.pandc.org/peter/work/ Assistant Director, Multimedia Systems tel:+1-614-728-3600;ext=338 OhioLINK: the Ohio Library and Information Network Columbus, Ohio The Disruptive Library Technology Jester http://dltj.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEhIv74+t4qSfPIHIRAoqDAKCBWZHEju0+K9VkYw2gpsDV3iIlDQCfUl+R AGhGIzRo8TMoj+23PfiZPNg= =Nadl -END PGP SIGNATURE-
Re: [CODE4LIB] next generation opac mailing list
I would subscribe to it. Kevin -Original Message- From: Code for Libraries [mailto:[EMAIL PROTECTED] Behalf Of Eric Lease Morgan Sent: Monday, June 05, 2006 12:41 PM To: CODE4LIB@listserv.nd.edu Subject: [CODE4LIB] next generation opac mailing list What do y'all think of the possible creation of a mailing list called "next generation" OPAC for libraries -- ngo4lib? The purpose of such a list would be to discuss things like but not limited to: * who would be the audience of such a system * what such a system might contain * how such a system would be created -- Eric Lease Morgan Head, Digital Access and Information Architecture Department University Libraries of Notre Dame (574) 631-8604 I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
On Jun 5, 2006, at 3:54 PM, Peter Murray wrote: Perhaps I'm too much of a radical, but for me even leaving "OPAC" in the mailing list name would be to already admit defeat. Yes, but we have to start somewhere. Change is incremental. IMHO, the "next generation" OPAC is not really a online public access *catalog* but something else such as "tool". These are the sorts of thing I see being discussed on such a mailing list. -- Eric Morgan University Libraries of Notre Dame I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
Well if you created it, I would join and participate as this is certainly one of my major areas of scholarly interest. However, a small part of me thinks I need another mailing list about as much as I need another hole in the head. Ed C. Eric Lease Morgan said the following on 6/5/2006 3:40 PM: What do y'all think of the possible creation of a mailing list called "next generation" OPAC for libraries -- ngo4lib? The purpose of such a list would be to discuss things like but not limited to: * who would be the audience of such a system * what such a system might contain * how such a system would be created -- Eric Lease Morgan Head, Digital Access and Information Architecture Department University Libraries of Notre Dame (574) 631-8604 I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
Re: [CODE4LIB] next generation opac mailing list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Perhaps I'm too much of a radical, but for me even leaving "OPAC" in the mailing list name would be to already admit defeat. Peter On 6/5/06 3:40 PM, Eric Lease Morgan wrote: > What do y'all think of the possible creation of a mailing list called > "next generation" OPAC for libraries -- ngo4lib? > > The purpose of such a list would be to discuss things like but not > limited to: > >* who would be the audience of such a system >* what such a system might contain >* how such a system would be created - -- Peter Murray http://www.pandc.org/peter/work/ Assistant Director, Multimedia Systems tel:+1-614-728-3600;ext=338 OhioLINK: the Ohio Library and Information Network Columbus, Ohio The Disruptive Library Technology Jester http://dltj.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEhIv74+t4qSfPIHIRAoqDAKCBWZHEju0+K9VkYw2gpsDV3iIlDQCfUl+R AGhGIzRo8TMoj+23PfiZPNg= =Nadl -END PGP SIGNATURE-
[CODE4LIB] next generation opac mailing list
What do y'all think of the possible creation of a mailing list called "next generation" OPAC for libraries -- ngo4lib? The purpose of such a list would be to discuss things like but not limited to: * who would be the audience of such a system * what such a system might contain * how such a system would be created -- Eric Lease Morgan Head, Digital Access and Information Architecture Department University Libraries of Notre Dame (574) 631-8604 I'm hiring a Senior Programmer Analyst. See http://dewey.library.nd.edu/morgan/programmer/.
