Page Tree:

Child pages
  • January 2011 Meeting - Work Area Demo Presentations and Notes

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

Skip to end of metadata
Go to start of metadata

Upload presentations and meeting notes about Work Area Demos to this page.

HUBzero demo - Bruce Barton

(Demonstration running under VMWare on Bruce's laptop)

  • Resources, public or private, individual or group ownership; may change privacy level, e.g., make something public after a time of working on it privately
  • HUBzero concept of "workspace"
    • "Virtual Network Computing (VNC) session on the hub."
    • Everybody gets one with account creation
    • Debian Linux shell environment
    • programming languages/environments available: Python, Java
    • anything for which there's a Debian install package can be added; or build from source
  • Can run tools applicable to problems like those described in Corpora Space last week
  • Strengths and Weaknesses
    • Strengths
      1. Tools development environment
      2. General tools and languages
      3. Support infrastructure
      4. User experience extensibility through Joomla-contributed extensions
    • Weaknesses
      1. Object store not organized around scholarship
      2. Tool model focused on simulations rather than application to objects


John Pybus: Where does one store the product of running a tool?
Bruce Barton: Within workspace possible. Can develop a tool in one's private workspace then make it available more publicly
Tim Cole: Shipping object to a remote service – mechanism in place?
Bruce: Yes. But getting back a response (derivative, let's say) w/ provenance metadata automatically applied is not there yet. We're thinking about how we might implement that. Perhaps a Fedora back-end to HUBzero. Object marshalling for the purpose of this kind of service call is also on our roadmap.

Alfresco demo - Noah Wittman

  • Alfresco is an Enterprise Content Management (ECM) platform that comes from commercial open-source space. In use at UCB for more than a year; preparing for a release of a general campus service we're calling "ResearchHub"
  • Configurable dashboard; "dashlets" – might include a "dashlet" for TSR, Bamboo Person directory, etc.
  • Project Sites can be created. Can be private/personal or open for collaboration. Site-wide dashboard, calendar
  • Document library. Nice interface for managing multiple documents in hierarchical organization. Generation of derivatives (e.g., of Office docs, of images), text indexed from content in things like PDFs, MS-Word – not OCR – (also could extend to recognize additional document types/formats)
  • Rules Engine: create a new one or link to existing .... based on conditions about an event (e.g., document upload by a person, where the document is an MS-Word doc) one may specify, perform one or more actions (e.g., convert to PDF) ... and one of the things one can do is execute a script, e.g., one that calls a service


Tim Cole: Available for deployment in multiple places?
Noah Wittman: Yes. With considerable amount of setup.
DAG: Multiple deployment models: institutional spin-up, consortial operation for multiple institutions, etc. Will see in Success discussion.
Tim: Moving data in and out?
Seth Denbo: Workflows – apply to a sequence of services
DAG: Yes, capacity to build this kind of script is built in.
Noah: Yes
Martin: This is very powerful. Much more interesting than something like Blackboard. Might one put TextGrid functionality – editorial workflow – into something like this. Is that a different animal? XML editing, linking to various kinds of lexica.
Noah: Same sort of features in a lot of web based applications. Question might be, is there any reason to leave TextGrid, is there something TextGrid does that this doesn't, or the other way around.
Tim: You might want folks to use an environment they are used to – but want the environments to communicate with each other.

Oxford VRE-SDM - John Pybus

  • Virtual Research Environment for the Study of Documents and Manuscripts
  • Implemented now as portlets
  • Virtual examination of manuscripts that are difficult to decipher as a replacement (or augmentation) for gathering scholars around a physical table
  • Screen-sharing to share images and point to points in the image as an on-screen activity ... augmented by audio, for real-time discussion of what different scholars believe a mark/letter/word/line to signify
  • Links to lexicons of names
  • (This was a very quick and superficial demonstration of some of VRE-SDM functionality)
  • Vision of adding functionality not by implementing new portlets, but by accepting open social gadgets as elements that can be incorporated into dashboards

Tim Cole: How are annotations stored?
John Pybus: RDF data store, currently available only within VRE-SDM, but could be exposed otherwise
David Greenbaum: A reason to invest in OpenSocial is to discover the degree to which we can expose tools, sets of tools, or even environments – that we can embed them inside non-native environments – so long as those non-native environments implement an OpenSocial container?
John Pybus: Right.
Jim Muehlenberg: HUBzero has built-in mechanism to call out to a grid ...
John Pybus: Would like to implement our environment on top of that or similar, widely-supported (consortially-supported) infrastructure
Jim Muehlenberg: Images, Audio, etc.?
David Greenbaum: Text relation to images – images of textual materials – so initial engagement with text give us some inroad into dealing with images. Not all. And certainly not yet into audio.
Neil Fraistat: Larger question about the three projects we've seen – interesting, somewhat overlapping functionality – causes confusion about what we're doing – if I could have started from scratch in Bamboo, I might try out these three and build the one that incorporates the best of the bunch
David Greenbaum: Approach we took supposes there will not ever be one environment. A few is better than ten. So we're doing that experimentation now, and considering what long term investments to continue. Open Social was interesting not only because why Oxford doing and because the connection with the future possibilities of Sakai which is in many institutions of higher education
Jim Muehlenberg: One idea might be to think of Corpora Space as the path forward having engaged with these technologies in Phase One?
David Greenbaum: Starting point was to take a small number, do some experimentation, then determine in which direction(s) to go forward.
John Pybus: With VRE-SDM we're starting from one environment, but hope over the course of Bamboo to see whether we can rework it in a manner that they can be deployed into other environments that are more common
Neil Fraistat: Very confusing still, where does one go to do what. Would like to see these clearly defined, how one is different from another, in which use cases one would use one, in which use cases would one use another.
John Coleman: OpenSocial: diversity of building things that can be used in multiple environments is the win. One environment for all is simply not doable.
Neil: Yes ... we need to articulate that story. A goal for success of the project ought to be that we push through to a more articulate focus re: what we're doing.

This right-side column is an artifact of "old-style" navigation. Please remove sections, columns, and content of the right-side column when this page is next edited. Cf. the Wiki navigation changes - July 2011 page for a 'how-to' on removing old-style page markup.