This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
Presentations available on this page:
Jim Muehlenberg: How will we decide what tools or service capabilities to integrate into Work Spaces
Bruce Barton: Several things: what's possible, who is willing, what we learn from pilots
Jim: Who's going to be in the pilot, tools to meet their needs, if we don't have tools to meet their needs how can they participate in pilots, etc. Chicken and egg.
Dave Lester: Tools considered? List on wiki?
Bruce: Scholarly services listed in the proposal, e.g., Concordance. Also, based on use cases we have, experiments in Corpora Space. We'll look at whether any of these can be deployed as tools
Ian: Outside services – from WS to digital repo such as CDL; pull Zotero collections into WS
Martin Mueller: Why bother having Philologic service in a work space
Robin Valenza: Doesn't work for most collections. Standard access to it and how data interacts with it.
David Greenbaum: One way to answer Jim's question is to consider to whom we are providing value. Who are our primary audiences? Is it a broad set of scholars who may not be doing the type of work that has come before in Philologic, then we need to make sure that tools we include are going to satisfy some of their needs. Work Space investment is for broader audience. We'll see a bunch of tools that come bundled with Work Spaces platforms on which we're building.
Bob Taylor: Cf. this morning's notes and presentations for a look at "sub-areas" of CI area of work.
Tim Cole: Looking for input re: candidate collections to consider for addressing interoperability. This list is open for contributions until Monday (31 Jan 2011) ... please contribute!!
Tim Cole: Bill Perod's "operations" explorations might be fruitful sources of services to deploy on the BSP, either in Phase One or Phase Two.
Neil Fraistat: How many collections are you aiming to finally arrive at
Tim Cole: A dozen on this list, we'll probably order them because addressing all is not likely. The list to be closed on Monday is the candidates from which we will draw our prioritized collections.
Neil Fraistat: We could use a more integrated strategy here. Some collections will be amenable to application to the services that we're focusing on.
Jim Muehlenberg: Comes back to audiences.
Neil: We may be in larger chicken-and-egg, but we must make strategic choices
Bob Taylor: Venn diagram
David Greenbaum: Hash into this later this afternoon?
David: Can't leave this "as broad as possible"
John Coleman: Not too much angst over audience. Tools and collections that exist do have an audience.
Neil: Pick collections with plenty of user buy-in. Representative selection.
Presentation: Scholarly Services on BSP - Status (PDF)
[SJM has no notes here – was presenting; these are Marlita's notes from facilitating]
Jim: White papers still on the map?. Is that less of a pattern now?
Neil: Less so, we think. Workshop 2 for CS – not sure what that might be. But let's consider what we lose if we do away with the idea of white papers. keep in mind big picture vision
Tim: Must capture what comes out of the workshop
Jim: Big picture vision implicit in white papers. Camp concept is bottom-up.
Neil: W2, however framed, must be about larger picture
Martin: "In the beginning were the tinkerers" (Der Spiegel)
- How to decide which tools first?
- User feedback
- Pilots - doing Pal work
-- What tools are under consideration?
-- Who is the primary audience that will help answer this question?
- Content Interoperability
- Candidate collection and profiling
- CI/Bamboo object profile
CMIS Workplan = WS = CS schedule alignment
Working: Get to people
Not Working: Lack of time -- Working groups vs. large meetings
- Please review candidate collections and weigh in
-- by next Monday will have it final/prioritized for Phase 1
- work with TSR -- how many WILL be done?
- work with WS
- Looking to automate operations
- Need to decide as a project intersection of:
- Come up with logic of collections chosen.