"Data Management: Curating, preserving; update/maintain software; geo-references" (Ex 3, 1a-E)

"We need bibliographic file management that fits idiosyncratic workflows" (Ex 3, 1b-C)

"I don't have the two years to mark it up in xml and find a programmer to do the dateline, etc. I'd love to take my primary materials and dump it into something that would do more for me." (Ex 3, 1c-D)

"My major critique of Bamboo is that it doesn't sufficiently emphasize the diverse and multiple uses of tools and material, and the ability to pull different sets of data captured for different purposes into single sites for new insight." (Ex 4, 1d-A)

"big question but small part of it: somebody (libraries) should provide a service that allows lowering of threshold bar for making repositories(huh?) example of access to nyu lib. architecture buld in abstract ways. builf for afghan libraries, now looking at using for collections of images. successful consortial efforts: JSTOR, ArtSTOR, interface not what i'd want but saves our library a lot of pain. can these be seen as analogs at a different scale for collaboration facilitation? jstor, artstor... what other stors? there's not a lot of humanistic methodology embedded in jstor. a title is a title." (Ex 4, 1d-F)

"Personalization in scholarly context - more than the ability to annotate and search on annotation and organize by it? I can imagine an argument that all I need in scholarly context is to store materials I have-- as long as I can link back, I don't care where they are-- but the environment notion" (Ex 5, 1c-D)

"Isn't it about tagging and bagging? Bagging into conceptual bins, maybe one object in multiple bins. Tagging w/ something that distinguishes in those bins, or strikes you, something that's a mnemonic. This would really work for hybrid system; whether you're in research library looking at document you can't take away, or have digital file - if there's enough of that tagging to get you back to it, and can put into multiple categories... If you could set up some kind of paradigm saying these are important categories and tags, these are kind of what Windows does in Word, it's slightly inefficient but it wouldn't take care of hybridity but would give you access. Once I have those photocopy pages, there's a physical process of juxtaposing pages. You put the materials together, you could do it on the screen, but the problem is hybridity of documents. More than bagging and tagging, also ordering. Also difference where while you're doing project work, they do take an awful lot of time to do (workflows, databases, ways for people to manage information) but it's different when you're doing your own thing" (Ex 5, 1c-D)

"We haven't had new hires lately. New grad students use blog like environments to relate, communicate, think about their content. Relational links. One place where everything is. Text, images, other modalities. Virtual desk. RSS feeds, links to other sites they find interesting. Totally different from 'my' practice. I have different sites. Stacks of printed articles. I don't like to read online. They are much more comfortable reading online. I use a lot of paper." (Ex 6a, 1a-C)

"development of lots of labs. Immersive, collaborative, accessible, visual" (Ex 6b, 1a-A)

"One interface that allows for the use of services all over the world. New services are added, new texts are added, so no need to learn something new. A service repository that is intelligent. Aggregation service. Actively filtered. Portal that mentions the tool you're working with, but with interoperability for different available services" (Ex 6b, 1c-A)

"If we know how environments work behind the interface, we can work more effectively with interface" (Ex 6b, 1c-A)

"No need to anxiously consult IT people, instead having a console of sorts. Tools and artifacts instantly available. Personalized ensemble of tools" (Ex 6b, 1c-A)

"Want coherent interface to the entire scope of your scholarly universe. You don't want to have to remember that pressing the back button destroys browser session here, but it's essential to work there" (Ex 6b, 1c-C)

"Going back to interface, starting point, flexibility. People can create their own, flexible starting point. People can tailor to their own needs instead of having to deal with stuff that looks and behaves differently" (Ex 6b, 1c-C)

"Now that its an open project, everyone can use it. If it works on one campus it will be available to others." (Ex 7, 1a-D)

"Infrastructure layer should be robust. Application layer can change and tweak. In a virtual environment you can have stable and dev versions of apps." (Ex 7, 1a-D)

"tool: iterated development, overarching architecture, modules connected by APIs, scholarly workflows (Sakai). toolset. platform and services. aggregation of tools, projects, interested people; maybe hosting. registering and aggressive research, discovery. standards body: data exchange, tenure, data curation (OKI)" (Ex 7, 1d-E)

"if Bamboo can be a collaborative space then can be useful " (Ex 7, 1a-H)

"Providing toolkit of options so you can do multiple things; work or conversation or finding a citation; can pick and choose and put together in a modular way" (W2, Scholarly Networks, plan, plenary notes)

"iGoogle, where you assemble the bits & pieces that work for you. You can take out the audio, for example, if it interferes w/your thinking." (W2, Scholarly Networks, group notes)

"Part of what Bamboo has to be about is autonomy." (W2, Scholarly Networks, group notes)

"I am creating a database on the history of evolutionary and developmental biology. I am currently using two tools. The first is Zotero, an in-the-browser, reference management system. We use Zotero to keep track of key primary sources (scientific papers, images, video clips, etc.) and to add annotations to our files. We will then use Omeka, an interactive, online, environment to share the files. We chose Omeka for its flexibility of functionality. Specifically, it allows for the creation of complex narratives from the database materials as online exhibits (incorporating media rich files), allows for folksonomy and metadata from users, allows for the collection of electronic artifacts online, and has full search functions for user access of database materials. My technological wish list would be for a patch that would allow Zotero and Omeka to work together. This way we could easily move between updating Zotero and Omeka. The other alternative would be to have an all-in-one working environment (file management, data collection, notation, video streaming, and tagging) that can also act as a robust publishing environment. The specific forms of expertise that I need at this point are a technologist to help me install and manipulate Omeka (hopefully she could help write code to bridge Omeka with Zotero). Also, I could use an information architect and a designer to help me design an attractive and workable interface. Finally, I could use some legal support to help secure permission for articles, images, and film and video clips." (SN-0006 The Extended Development Project - An Online Database on the History of Evolutionary and Developmental Biology, Phillip Thurtle, 1/5/09)

Bamboo tags: 

Add new comment