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
  • Workshop 5 - Demonstrators

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

Skip to end of metadata
Go to start of metadata

Exchange demonstrator

5:16

Project Bamboo:  Rick Peterson, Washington & Lee: We're a small place, hired one local programmer from San Francisco who wanted to get away to Virginia, did a mockup and developed it in about 3 weeks

5:16

Project Bamboo:  Added stuff as much as he was available; started out with Exchange focus, but due to Drupal, had to add in all the other stuff, so you get blogs and wikis and groups

5:17

Project Bamboo:  Cost $4k to pay him to do it, worth doing to explain to our faculty what we're talking about when we talk about Bamboo; had to show them something

5:17

Project Bamboo:  Have some paper slips with logins (guest and community members)

5:17

Project Bamboo:  Welcome any questions or comments, basically did it because we wanted to do something

5:17

Project Bamboo:  CJK: Picking up on the exchange stuff; addresses a few things

5:17

Project Bamboo:  There's technologies we can adapt to these purposes

5:18

Project Bamboo:  Every step was an opportunity to reference something in the Atlas

5:18

Project Bamboo:  You have who's submitted it, when, what group was it associated with - these are the automated things that are possible

5:18

Project Bamboo:  In 6 months, we really could overhaul our community environment

5:18

Project Bamboo:  We can bring more to our community

5:18

Project Bamboo:  The Exchange in the program document, like the Atlas today, was very ambitious

5:19

Project Bamboo:  Something as simple as a way to say "I've got a resource available, if you want some help" can be a demonstrator for a follow-on project for something more robust

5:20

Project Bamboo:  Q: This is useful to show to people what it is. But as something that we want to create for Bamboo, not so sure - not going to remember my username for something like that. Haven't established there's a need for us to put blogs, share job adverts, share project information - multiply number of places where we have to go for information

5:20

Project Bamboo:  Atlas: needs way to share information; people who write blogs are already doing it; need to pull things together, rather than making another place to put blogs

5:20

Project Bamboo:  Could be useful for sharing info in Bamboo Build project, but risks creating another silo

5:21

Project Bamboo:  Need something more open, not just one place we go to log in

5:22

Project Bamboo:  DAG: Helpful to have something to look at; Demonstrators are good for both showing what you want AND what you don't want

5:22

Project Bamboo:  Ways to take information that's valuable and expose it into existing collaborative/virtual environments

5:22

Project Bamboo:  Drupal - example of collaborative/virtual enviornment

5:22

Project Bamboo:  For any environment, capture from it/expose info to it

5:23

Project Bamboo:  Helps us think about what we want, what already does that, and what the right investment is and may not be, and why

5:23

Project Bamboo:  Fast cycle projects like this so we have more things to show, more things to discuss



Atlas demonstrator

Presentation Slides (PDF, 5.75MB)

4:31

Ideas for a demonstrator for the Atlas

4:33

Steve: A demonstrator project that is aimed at fleshing out more concretely and less conceptually what we mean by Atlas

4:34

Way to think about this at this point: idea of PB atlas as appropriately narrowing scope talked about earlier

4:34

Don't want to reprise W4 presentation, but we've talked about a deep and structured understanding of humanities practice, from the beginning of project

4:35

Got to a point where we think that there are more or less a set of elements/entities that can describe what technologists and what scholars mean and librarians, and so forth

4:35

Pieces and perspectives from which practices can be understood

4:35

Concept of Atlas - take those elements, take facility for decorating them with metadata, what's the value/meaning/rating/expert's evaluation/community uptake

4:36

All definitions of the elements that we've talked about

4:36

Talked more about scholarly methodology than shared tech services

4:36

Kinds of interactions - rating and reviewing, contributing, categorizing, etc

4:36

Doing this as individuals, communities of intterest, etc

4:36

Search and discovery

4:36

What we haven't done is going from conceptual model to asking "if this thing existed, how would you approach it?"

4:37

In doing demonstrator, asking those questions

4:37

What would the deliverables be? Part is design, grounded in consultation

4:37

Includes at least some well-curated seed content

4:37

Right now on wiki is around 60 narratives, 90 activities, very few recipes

4:38

Very little connection/analysis

4:38

We have some curation that needs doing

4:38

Demonstrator = actually works (working services, a test-drive interface)

4:38

What would each of those things look like? Caveat that this is a proposal for a demonstrator, needs to be shaped by participation of people who would be interested

4:39

Put out in a number of e-mails leading up to this - after this agenda is done, there's another meeting to talk about this demonstrator project

4:39

That meeting could completely reshape it

4:39

Four deliverables can be thought of as four quasi-independent but related strands of work

4:40

Deliverable 1 - design grounded in careful consultation

4:40

User-centered design (cf Fluid)

4:40

Looking at candidate interfaces - how would a person use a particular service?

4:40

Consult with diverse stakeholders-- scholars, librarians, comp scientists, technologists

4:41

Probably not true that each will want to approach in same way

4:41

Have to ask many different kinds of people how they'd open the atlas

4:41

Figure out necessary interfaces

4:41

Consider full range of uses that might come up

4:42

Different people will be looking for different things

4:42

Data mining one's own publications, find what matches it in some way

4:42

Stuff that requires this particular markup

4:42

Best practice in rating

4:43

Want to consult with potential users - is this way of showing ratings useful to you?

4:43

Best practice in algorithmic search

4:43

Best practice in citation and referral

4:44

Don't want to get stuck building a working interface for each type - can handle this by using wireframes

4:44

Sketch something up

4:44

Can literally have pieces of paper that you shuffle around

4:44

Can literally be hand-drawn sketches

4:45

Deliverable #2 - solid body of well-curated "seed" content

4:45

We have some materials already; needs curation/analysis

4:45

Focus on depth rather than breadth

4:45

Focus on 1-2 small areas, a well-curated body of content related to that

4:45

Right now, curation going on -- deepening Atlas linkages

4:46

Grad student from Berkeley information school, looking through sets of narratives

4:46

Decomposing narratives into steps, forming recipes specific to narratives out of those steps

4:46

Then trying to extrapolate some additional possible recipes based on what can be generalized

4:47

Generalized recipes -- taking specific steps, looking at recipes that'd apply to several narratives at once

4:47

This isn't the be-all, end-all analysis

4:47

What would it mean for that to be a strand of work?

4:47

Gathering additional content, esp if we decide to focus on a disciplinary area with some gaps in the wiki

4:47

Deliverable #3: something that works

4:48

One could be building some services that deliver limited/core functionality: model and implement

4:48

Alternative: look at something out in the world, do some modeling exercises, see how what we think we need matches w/ something that's already been built

4:48

Fathom project

4:49

Look at project going on at UVA developed w/ a distant eye on what's going on in Bamboo

4:49

See whether that can be a part of our working demonstrator

4:49

Thinking about things that would be in Atlas, interactions/activities one'd want to do with those things

4:49

Entity relationship diagram - narrative > recipes > (activity, tool reference, content reference)

4:50

Narratives and recipes have a relationship, and there's metadata/meaning associated w/ these things

4:50

Reviews, ratings along various spectra, tags, other annotations

4:51

Might approach from engineerin-model idea

4:51

There's metadata on relationships, too

4:51

Rating or reviewing relationships-- doesn't really relate, exactly on the mark, etc

4:52

#4 - Working Atlas-demo "test drive" interface, beyond wireframes, something the community can test-drive and provide feedback

4:52

Timeframe

4:52

Series of "sprints"

4:53

Whatever work we do, esp if in parallel strands, will be divided into short periods w/ defined goals

4:53

Align the strands between those period

4:53

Delivering proposal will take a fair amount of bandwidth; may not start until August, shorter sprints

4:54

Might start even well into the fall

4:54

Maybe spill over in January if implementation won't start until Feb

4:54

Can figure out over the summer

4:54

Depends on who wants to participate, how, what resources, etc.

4:54

Chicago and Berkeley will participate

4:54

Atlas-focused Bamboo institutions

4:55

May be enthusiastic community members, regardless of institutional interest

4:55

Shakespeare quote from Henry V

4:55

Questions?

4:56

Q: Talking about Atlas as interface, but after change re: Scholarly Network doing interface, does that change?

4:57

Steve: Doesn't matter what area of Bamboo delivers it, trying to get at, if you as a user were to approach this, what would it look like (wherever you do it)?

4:57

A services API isn't so useful for end-users

4:58

Services behind those interfaces

4:58

Jim: Putting a plug in for this project - sustained energy from April to now, might fall off if we don't have something to keep ourselves busy with

4:59

Concrete, way to carry momentum

4:59

Primes us well for January

4:59

Good way to test out theory we've thrown around for a year, get us started

4:59

DAG: Other questions?

4:59

Arno: Key point on depth vs breadth

4:59

Edited/curatorial approach

4:59

Hopefully will address scope concerns

5:00

Not The Place for all X tools

5:00

That's not sustainable/possible

5:00

Still worried about relationship of this work to the way scholarly narratives are being conceived

5:00

I voted no on the current conception of scholary network

5:00

Worry about the ability we'll have to aggregate important work you pointed out in one place

5:01

If I'm in Blackboard/Facebook/etc and have a view on the Atlas, and want to rate something, not clear that Sakai/Facebook/etc will allow that rating to migrate to another virtual environment

5:01

Maybe some fragmentation is ok - local rating/comments, and global

5:01

Different lenses will provide different views onto same thing

5:01

Tech challenges of making it work w/ scholarly networking vision as stated, that's significant

5:02

Worried about scholarly networking, not atlas

5:02

Steve: Perhaps one of criteria for thinking about which scholarly networks Bamboo provides a gadget/widget into, could be the ability to have two-way conversation

5:02

Q: Less idea of why anyone would do any of this, right now, than this morning

5:03

What's the connection between what happens here and teaching/research

5:03

This has been going on for a year - would expect that analysis of what people were writing, doing, etc be done by now

5:03

Don't have anything I can take to anyone and explain why it's compelling to do right now

5:03

We don't have "this is what it's going to do in a time of crisis"

5:03

We don't have "this will re-invent education"

5:04

I'm here because I have a vision, and this is fine, but you're missing the starting point

5:04

What would I tell people they were getting?

5:04

DAG: Let's pick that question up tomorrow morning

5:04

This is one major area of work out of 2-3

5:04

Services platform is another argument in favor of value

5:05

Question is good for a reflection of whole discussion

5:05

Will be future opportunities to participate, even if you can't join us for the conversation tonight


  • No labels