This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
• Humanities inform IS/CS
• Communication between groups
• Not too much focus on tools & applications
• Approach to make the JW work
• Room for creativity & open endeavors - conversation, experimentation
• IS/CS <-> H (crossing boundaries)
• Looking at same concept with different lenses
• Pattern/similarity/productivity vs. variations/incompatibility/performance
• Interdisciplinary conversations & inter. cog.
• Communication - needs structure
• Open source/open access vs. proprietary (not a binary distinction)
• Artistic, creative uses of technologuhies
o Transform ed/scholarship
o Identify shared services
o Developing collaborative practices
o Promote/advocate for digital scholarship
o Herd cats/dogs/pigeons effectively
o Be/create the tipping point to bring about an "aha" or wow factor to humanities scholarship
o How can Bamboo be made more visible?
o How can Bamboo adapt/use what's already out there?
o How can Bamboo facilitate information sharing among the community?
o How can PB articulate the incentives/rewards for building shared services?
o How can PB manage/reference ownership/responsibility issues for the sustainability of the enterprise?
o How are the infrastructure needs of the arts & humanities different from STEM communities?
• 'Find stakeholders'
• 'Institutional boundary'
• 'Subtlety + competing desires'
• 'Where are the grad students?'
• Using Bamboo process as a model for central IT to understand scholarly practices
• Legitimize new scholarly process enabled by shared method - -ologies and concepts, at the interface of information science & humanities
o w/ canonical examples
o e.g. Powerset + ASP
o CSPAN database
o Prompt the discussion
o Re: standards, funding, promotion and tenure
o Produce replicable models (sustainability)
o What is Bamboo's unique contribution?
o What sort of advocacy
o Incentives for humanities scholars?
o How to introduce digital tech methodologies to students
o Are we after transformation or simply improvement?
o How can Bamboo keep up w/ changing technologies?
o What were the origins of Bamboo?
o How much is Bamboo strictly web-services oriented?
• Promote interoperability of data & tools - on the basis of relatable ontologies
• Adopt open source/community lead + champion?
• Induce change in scholarship practices (more collaboration, openness)
• Should produce/build tools to support previous
• Facilitating collaboration & community
• Changing relationships among stakeholders (external/internal)
• Humanities flourishing & defining their own agendas
• Services vs. tools
Back to top.
What will Bamboo accomplish?
• Building on the experiences from prior digital projects
• Give feedback to vendors
• Move towards commonalities & standards to enable shared access
• Assist small-scale institutions
• Validate tech-based scholarship in tenure & promotion
• Raise awareness of technological capabilities among faculty
• Raise awareness of technological learning curve for faculty
• Yocha: Benkler - commons-based peer-production
• How will Bamboo peer review our suggestions?
• How will Bamboo integrate other group projects?
• How digital content creators overcome copyright and intellectual property issues?
Back to top.
(pb1c-053, 055-058; 061-062)
Hopes, Questions, Observations
* High interest in Bamboo as a good basis for setting standards of collaboration, interoperability, critical mass -> body bringing us together
* Sustainability, but extend facilities like research assessment
* Tools, but let's get tools suited for purpose
* Find the info we want - i.e. content
* Define the ground rules for digital scholarly practice - or where are they
* How to find out where tools are and how to use them
* Directions to right tools - training
* Glue tools together, making them usable, approach tools in different way
* get trusted advice, not always case from IT; use graduates to fill gaps; straddlers
* Use non-textual media (including) (>), text and primary by other media; need tools for this
* Finding segments in fine-tuned media
* People aren't aware of tools
* Need tagging opportunity > education
* 2 types of textual analysis
* Every humanist a collaborator king
* It's hard to get credit for collaboration
* Libraries work to know what content, relevance, work + tool
* Streaming; files, ruining image
* Links with broadening (>)
* Impact on indexing
* Bottom-up approach not attribution - gluing everything together requirements - in hope!
* New to identity, what are the emerging technologies, agile reaction
* Wide range of initiatives, tools, interoperability, how does Bamboo deal with this?
* Tool discovery happens in the pub
* Should we make the pub global? Is this sustainable?
* Search can be "eccentric"
* Tools are hard to find because of incentive/cost
* Make services citable - robust citations
* Stability of URLs when citing
* No credit for those past citations
* Full-time job to keep up w/ tools
* Social networking - helping people share what they are doing
* Social networking is a 21st century pub
* How can these tools be built cognizant of an ever-changing environment?
* As we look at projects, how do we assess long-term usefulness?
* Note/Track topics of research
* "What is going on?" - use of social tagging
* Can Bamboo help institutional infrastructure/networking?
* Multiple choices
o Engage w/ the university
o Engage w/ the project
o (Maybe 'consume it')
Back to top.
* Time to learn
* Prod. vs process?
* Reliance + durability?
* Funding alignment
* Lib vs. archive
* Scale IMO hum.
* Enclave vs. open
* Lib + interoperability
Back to top.
* How do we engage the EU initiatives more collaboratively?
* Not duplicate EU-wide effort
* Be able to engage individual resources
* Reliable way of knowing
o What's out there
+ Individual research
* "Enhancing the Pub"
-Specifics to do with regional nodes
-Emergence of differentiating behaviour from discrete disciplines and their impact on shared technology services
-Historical moment (the time is right)
-Finding a balance between visions of technological futures and finding solutions of a practical nature to existing and emerging problems (Hope from Bamboo)
(pb1d1-02 to -04)
-Data formats: "user-supple" and easily migratable
-Multiple-language editions of digital text
-Copyright and law issues "interfere" with base work of scholarship
-Are programming and law orthogonal to scholarship? Maybe not
-What is the potential of virtualization?
-Community-driven projects: Planning focus vs. lack of central direction
-What does it mean to archive? Robust and innovative definitions
-Longevity: Why do DH projects die? How can they be preserved?
-Generalized vs. contextualized. How to achieve both
-Federated services, integrated, Web 2.0
-A&H ethos, recognition, reward, funding---relation to collaboration in A&H. Will institutions support? How to sustain beyond end-of-project?
-Longevity and sustainability
-What is 21st century arts and humanities scholarship? What is "skill set"? How to train?
-Who is the community?
-What is the domain?
1. Community Building
-IT, libraries, researchers
2. Make Tools/Services Available
-easy to find and use
-don't reinvent the wheel
3. Get Buy-In
-fields of study
-Method of communication to facilitate connection between needs, resources
-Means of educating faculty in technological literacy---invite participation
(pb1d1-07/19 and 20)
Community vs. Scholarship
-How to apply "Wikipedia-like" governance for community involvement
-Where are boundaries drawn around a given "object" that both allow and prevent community engagement?
-Bamboo can become big enough/open enough to encourage large-scale community contribution
-Build small projects that are "doable" and that speak to one another
(pb1d1-08 to -11)
-Repositories that serve scholars/scholarship---to do what we need, not what we can
-Inst. repository---new problem: great quantities of data
-How to maximize access to data?
-Support people inputting that data?
-Bamboo to help outside of inst. boxes---How to push collaboration outside of inst. boundaries?
-Thinking along disciplinary lines versus corpus (campus?)---find similarities.
-Money from institutions---but use instead of importing and exporting data.
-Traceability through record---across UI/Application sensitive to possible use cases.
-Chaos, change and loss but work optimistically
-Those at risk because of all the one-offs
-Don't throw anything away casually
-Rise of meaningful underground research visibly persistent
(pb1d1-13 to -14)
2. Brokering involvement from outside academia
1. Common infrastructure inhibiting innovation
-reuse, e.g. Napster
3. Social organization
-organic vs. top-down
-way for humanists to share
-DRM/security vs. fair use: in scope for bamboo architecture
-Concern that a bamboo failure will serve only to discharge much energy
-What message should go to related communities?
(pb1d1-15/16 to -18)
-Standards need to be defined/determined
-durability of data
-still need room for innovation/idiosyncrasies
-standards foster creativity
-Is Bamboo a thing, or is it an ethos, way of doing things?
-a toolbox or a community...both
-academic "Craigslist" of skills
-What is the tipping point at which these tools become a standard way of doing things?
-Does the few number of faculty here change the conversation?
-speaking on their behalf?
(pb1d1-21 to -30)
Narrative of Humanities Scholarship
"Condensing meaning from the vapor of nuance." - Neil Stephenson
-Best practices docs.
-Aggregate "_________" into a super wiki - "Academic Commons"
-Use learning management systems
peer review of course site
-all individual authors/reviewers
-Bring disparate data together
-properly document/annotate "mounds of data"
-Create = language understanding
zoological data, environmental data, music
biological data, photos, GIS
satellite fire maps
video, social history
-Immediate synchronous annotation
-Archiving data -
-Transform offline data
Looking at material corpora
Assessing meta structuring
Find a better ontology
-Build a database of images, digitizing
-tagging is a "burden"
-elaborate on data that gives meaning to someone else
-stream of consciousness connections
-I relish because it is machine-actionable
-researching archive material
-stored in database
tagged/marked up - text, images
-merge visual w/textual
-Evangelizing faculty to allow digital research
-"Bring it all out into the light"