Scheduled DB Maintenance: January 21st - 8:00 AM to 10:00 AM. Confluence will be unavailable during this time.

Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Ex3&4 flipcharts

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

View all flipcharts

Leadership

Flipchart photos

W2-Leadership-1
A) TITLE
LEADERSHIP - to serve as catalyst

  • Could be subsumed into oversight body at some point in future, given its cross-cutting directionality, but needs a working group at this point to address principles and what Bamboo needs to do to lead by example
    B) RISKS/REWARDS
    RISK - "Advocacy" - lack of consensus, questions of efficacy, shift in focus to "leadership"
    Project Bamboo as clearinghouse of resources
    REWARDS - Access to resources - data, scholarly networks, statements of principle, etc. - that will advance the mission of Project Bamboo
    C) SCOPE - porous
    Facilitator must stay in touch with all other groups
    IN: provider of information
    OUT: specific recommendations (P&T, etc.)

W2-Leadership-2
A) TITLE
Mismatch? - workshop 1 breakout questions, issues raised at workshop 2?)
Different things to different people
Cross-cutting direction
An issue for oversight body rather than "breakout" direction?
Issues: impact
Shift to resource/best practices and cross-disciplinary information clearinghouse/networks
Leadership role - B
"Mini-Bamboo"
Catalyst - set of principles
Just frameworks? Or support for projects, practical & applied?

Education and (Professional) Development

View flipchart

W2-Education-1
See diagram

Institutional Partnerships and Support

View flipcharts

W2-Support-1
WHAT WILL IT TAKE TO ACCOMPLISH THIS?
Buy-in from PB leadership council and their active participation along with broad-based volunteer effort from this community
DEMONSTRATOR PROJECTS
1) Presentation or V12 of principles that emerge from this 3-month planning effort (3 hr)
2) An information architecture for clearinghouse of information (3 wk)

W2-Support-2
ROUGH PLAN OF WORK
1) Set up wiki/online space for collective principles
1) Work with other groups to establish common set of principles brawn from work of all groups
2) Identify broad categories of info and resources with input from other groups for clearinghouse

MILESTONES
Formation of working groups

  • Nov 12: Initial call to groups to give feedback as to guiding principles
  • Dec 12: If no response, we will look for principles implicit in wiki materials
  • Jan 3: Last minute check in for comments/missing?

Network of Scholars, Researchers, etc.

View flipcharts

W2-Networking-1

  • Discovery/sharing
  • Social support/capital
  • Exemplary model (attractive/usability)
  • Social networking fatigue
  • 'SOCIAL' stigma (scholarly? education?)
  • Connecting networks
  • Mentoring
  • Hub of networking? (no time to learn new system)

W2-Networking-2

  • Contribute/distribute
  • Vision is important, technology should follow
  • Social networks evolve (provide tools, enable capability)
  • Draw on existing networks
  • Mailing lists
  • Discovery - resources, solutions (software, human)
  • Is it a working space or a networking space?
  • Copyright/IP issues? -> levels

W2-Networking-3
FEATURES/FUNCTIONS

  • Group/levels of access (e.g. Facebook)
  • Professional networking (e.g. 'Linked In')
  • Easy to use
  • How much should it link out? Or be the central space
  • It should evolve... provide the tools and it will happen organically

W2-Networking-4
e.g. Sunoikisis (virtual classics) dept
Odd case b/c it has incentive
e.g. TEI list (Text Encoding Initiative)
Facebook works becauase it's easy, it's brief & discrete, small grabs
Wiki has o parameters
What is the value?

W2-Networking-5

  • Share research - how to make a safe place to do that
  • Attractive to senior/junior scholars
  • Summaries a good idea
  • Current wiki is not a social networking tool
  • Scholars need to benefit
  • Interdisciplinarity
  • Levels of access
  • You-tube like widgets

W2-Networking-6
NAME/WORDS

  • Community
  • Bamboo network
  • Networking (active) scholars & scholarship
  • Commons/scholarly commons
  • Metaphors - grow, organic

Standards and Specifications

View flipcharts

W2-Standards-1
Domains: plumbing, metadata, practice areas
Liaison
Dimensions of "Standards"
Process = review? vet?
Don't create new ones
NNIH - Not Not Invented Here
Besides, there are too many domains involved in Bamboo
Communication, outreach, forum
Case studies

W2-Standards-2

  • Interoperability
  • Sharing
  • Preservation
  • Enable
    What should be the impact of whatever's done in "Standards"?
    What about where standards are lacking?
    Eg. ARTstore & image quality
    VRA - Visual Resources Ass'n
    Potential arbiters of this
    Quality, acceptance

W2-Standards-3
See diagram

W2-Standards-4
"Practitioner voice" often sought by existing standards bodies
RISKS & REWARDS

  • Credibility
  • Interoperability
  • Facilitating newcomers, scholars
  • Alienation, meddling
  • Critical mass
  • Tyranny of normalization
  • Longevity
  • Quality

W2-Standards-5
Scope (or out)
Authoring standards
Articulating value, recommending practices
Identify technical standards for the services framework (the plumbing)
Coercing usage, requiring
Quality assessment of digital humanities works
Awareness of existing examples of digital humanities works

W2-Standards-6
Top 3 agenda items for WG:

  • Organizational structure, identify types of participants
  • Rough enumeration of standards & best practices relevant to PB
  • Operational framework including articulation with other WGs

W2-Standards-7.1
Work items

  • coordinate "clearinghouse(s)" find, transfer, annotate

W2-Standards-7.2
Ana: meta

  • Executive/steering function
    awareness
    liaison
    identification
    prioritization

W2-Standards-8
Work items

  • Iteratively identify who will participate
  • Identify the fields and professional organizations connected with PB to ensure adequate participation -> Demonstrator
  • Develop representative list of standards issues to test the organizational structure and process we devise is reasonable

W2-Standards-9

  • Talk to participants, to formulate initial issues
  • Propose initial communication plan, to include the other WGs
  • WG liaisons meet with PB staff
  • How to decide whether to adopt, or what to recommend? A process and some principles

Interacting with Tool & Content Partners

View flipcharts

W2-Tools-1
Scope
1) Discovery & use layer

  • Tool registry
  • Content/resource registry
    2) Integration
  • Interoperable tools
  • Advocacy for standards
    3) Developing cross-cutting community
  • Simple/transparent roadmap
  • Use cases, case studies, stories
    (Know by example/models)
    (Template for NARRATIVES including viewpoints from scholar/users, developers, content providers, ASSESSMENT, EVALUATION)

W2-Tools-2
RISKS

  • Standardization doesn't meet needs (which are very nuanced and different among users)
  • Scholarly adoption of knowing & emerging resources & tools
  • Incentives for content providers & resource users
  • Avoid duplicative efforts, knowledge of existing initiatives
  • Loss of opportunity by evolving EXCLUSIVELY as a virtual environment

W2-Tools-3
REWARDS

  • Broad access/discovery broad & deep
  • Integration
  • Efficiency
  • Economy
  • Shared knowledge, marketplace of ideas
  • Interdisciplinarity
  • New research opportunities

W2-Tools-4
SHARING/DISCOVERY

  • Registry: Content - assets, data
  • Registry: Tools
  • Scholar networks: knowledge sharing via USER feedback about content & tools interaction
  • Registry: standards - environmental sow (question) and registry
  • Scholar networks: use cases/case studies
  • Discovery and use layers - Functionality: metasearch/query architecture, use/re-use environments, contextualize content who/what/where?

W2-Tools-5
Advocacy/Partnership
Cross-repository discovery & opportunity for data analysis

  • IP
  • Business case - how to incent content providors?
  • Technical challenges
  • Metadata mapping x-platform
    Scholar network
    Know community of users
  • Beta groups
  • User groups
    For purpose of use case, development of tool QC & testing, requirement gathering
    Seamlessness across repositories of primary source materials

W2-Tools-6
CONTENT DISCOVERY METHODS
Format, Domain

  • Broad-scale discovery (breadth)
  • Drill-down discovery (depth)
    Tools to support 'discovery' and use at multiple levels
  • Find - discover -> library perspective
  • Make order - use -> scholarly practice
    Need case studies/use cases to understand relationship between content repositories and scholarly uses (discovery w/ access)

W2-Tools-7
MILESTONES

  • Develop timetable and deliverable first for working groups
  • Develop a "straw man" for each of 3 scope items (e.g. what does a registry look like? What are the pieces/template for a case study?)
  • Use PB themes to cluster registry items (e.g. annotate resources/tools)
  • Define problem sets (what problems are we trying to solve for scholars? Born digital materials vs. analog originals)
  • Registry should include extg. & desired tools, repositories, use cases
    See diagram

W2-Tools-8
DEMONSTRATORS

  • Wiki for registry (domain tagged, activity-theme tagged, clusters that apply, degree of interoperability)
  • Use case/case study template
  • Generic workflow representation for scholarly activity which would be customizable by domain
  • Template for defining problem sets

W2-Tools-9
COMMUNITY - HUMANISTS
Clusters

  • Visual (static, dynamic - time-based)
  • Textual
  • Performance
  • Creators/analysts
  • Full spectrum of academic-engaged students -> senior academics
  • Spectrum of digitally "mature" users
    See diagram

W2-Tools-10
COMMITMENTS

  • Time (release time not available for current 3 mos)
  • Leadership/coordination for effort
  • Institutional buy-in for staff to participate in PB planning activities
  • $ for travel
  • Realistically - the only commitment that can be made for next 3 mos. is to add our comments/notes to PB wiki
  • Articulation of demonstrator projects

Interacting with Tool & Content Partners 2

View flipcharts

W2-Tools2-1
Tools & Repositories II

  • Staff
  • Partners, license, IP
  • Tool interoperability
  • Incentives for sharing
  • Question of identity trust

W2-Tools2-2

  • Content vs repository
  • Content is more inclusive term
  • Reflects scholarly thoughts
  • Collections? Data?

W2-Tools2-3
Access to "Content", "Data", "Repository"
1) Loss of control
2) Promote scholarship
3) Preservation
4) "Sensitive" content requires limited access
5) License and legal issues

W2-Tools2-4
6) Bamboo -> establish license protocol
7) Bamboo "communicate" repository information
8) License negotiation advocacy for scholarly use
9) Cooperative licensing

W2-Tools2-5
10) Interoperability issue for resources within our control
11) Develop a tool to establish scholar to pull content from multiple resources to view and use

W2-Tools2-6
12) Demonstrator projects to show possibilities of how to use content
13) Set guidelines and frameworks for software developers - have tools "talk" to one another' "Bamboo compliant"

W2-Tools-7
14) Bamboo can establish core tools
15) Rewards collaboration/scholarship re: budget
16) Performing "arts" - music? Where is the data?
17) Changing trends in scholarship?

W2-Tools2-8
Interoperable tools & content
To be done:

  • Identify core services
  • Identify demos
  • Identify rewards/incentives
  • Scholars at small schools
  • Tools available elsewhere; discover & use/blend

W2-Tools2-9
Potential Demos
1) Image tool

  • Multiple src
  • Multiple formats -> integrated display
    2) Multiple texts
    See diagram

W2-Tools2-10
3) Scholars oaister
Discovery
Identification
4) Entity extraction
dates -> simile
places -> Google maps

W2-Tools2-11
Partners

  • Jane Austin Proj
  • Naxos
  • P Prellinger
  • Getty
  • ECAI
  • MITH
  • D Rumsey
  • Manyesps
  • SEASR
  • Fedora/dSpace
  • JSTOR/ARTSTOR
  • Yahoo
  • Mozilla
  • Amazon (S3)
  • Google
  • Dan Cohen
  • TAPOR
  • VRE (dance)
  • J. Unsworth
  • G. Crane
  • MARTIN

W2-Tools2-12
5) Annotation

  • By media type
  • Persistence
    ex. - publishing a dissertation/thesis
    6) Middleware app
    Zotero -> square -> MONK, SEASR (see diagram)

W2-Tools2-13
7) Tool discovery & use
8) Scholarly BPL to stitch tools
Environment (visual) when scholar sequences tools (question)

W2-Tools2-14
Scholarly workflow
ex. get text from repo a (w/ parameter) then send to lexical tool then send results to visualization tool

W2-Tools2-15
Upward arrow, from Workbench (create flow), Execute a flow (interactive), Saved result set

  • No labels