Twitter: @ThatAndromeda
LinkedIn: AndromedaYelton
LibraryThing: Andromeda_Yelton
firstname dot lastname at gmail
Or drop me a line below.
Twitter: @ThatAndromeda
LinkedIn: AndromedaYelton
LibraryThing: Andromeda_Yelton
firstname dot lastname at gmail
Or drop me a line below.
Hi Andromeda,
I stumbled on your blog this evening. And I wonder if you’ve see this… Also expect you have…
http://www.boston.com/bostonglobe/editorial_opinion/oped/articles/2010/07/23/a_library_tells_a_story_of_its_own/
I like libraries and always look for these to wander in when I’m travelling. And I love HHR architecture, so I’m really keen to get to the Malden Public Library; and the Woburn Public Library. I’ve been to the Quincy Public Library a few times.
Cheers!
Marisa (Alto, HRC)
Hi, Marisa! What a great story. I hadn’t seen it yet, and now I need to make a trip to Malden, apparently (it is pretty convenient to me). I do have a couple of posts about library architecture (http://www.andromedayelton.com/wp/tag/architecture/) — the first one has my thoughts on the new Cambridge PL (among other things); the second has lots of pretty pictures.
Hi Amanda:
As one boundary spanner to another, note that all FRBR not-quite-theories presented so far which invoke “inheritance” are not aware that genetics has moved on past tree-like structures.
Note also that the opportunity to use network structures for bibliographic description was lost when biologists abandoned network structures after Darwin’s “Species.”
With phylogenetic *networks,* Biologists have now corrected their error — can we?
For *lots* more -boundary spanner friendly – on this, see this slideshow:
http://www.slideshare.net/RonMurray/from-mobydick-to-mashups
(For the benefit of any future internet wanderers who come upon this page, this discussion is in reference to my blog post http://www.andromedayelton.com/wp/2010/09/20/inheriting-from-frbr-merrily-smashing-some-things/.)
I don’t know that I buy the genetics analogy. For one thing, I think people have a variety of inheritance models, not just biology, to draw on (personally I was thinking of “inheritance” in its CS sense, where polyhierarchy is a familiar concept). Second, the discussions of FRBR I was involved in during school generally weren’t couched in terms anywhere near that technical, and didn’t think in terms of an inheritance paradigm.
At any rate, what concerns me about polyhierarchical models is implementation. For one thing, it’s a fraught question in CS — the difficulty of both polyhierarchical back-ends and their user interfaces is something that comes up regularly in conversations with my software engineer husband, actually. For another, I just can’t see how all the human labor of generating those cross-references will ever, realistically, be performed; I don’t think the resources are available, and I think the construction of those links is treated as far more simple than it really is.
I liked the monohierarchical model presented because it seems so much cleaner, both conceptually and implementationally. It definitely rules out a lot of options that a polyhierarchical system could provide, but I’d rather have something realistically possible to build than something philosophically intriguing that I can’t see how to implement. So if what you’re talking about here is polyhierarchical inheritance structures (which seemed to be the upshot of slide 19?), you first need to convince me on practical, not philosophical, grounds
.
Andromeda,
I am so very proud of the excellent work you are doing! You are a delightful person and a wonderful addition to our profession. Keep up the good work!
Thanks for your kind words!
Hi, Andromeda,
Remember me from SAT prep teaching in the summer of 2004?
I’m applying to Simmons GSLIS and would love to talk about your experiences there… and job-hunting afterwards
Wow, what a small world it is.
Bob Leigh
Wow, hi! I’d be happy to talk with you. Shoot me an email.
Hi Andromeda, it was a pleasure meeting g’day. Enjoyed your TEDx talk in Princeton and was amazed by your team opening 5 libraries in one month. Great job.