Dear All,
Matt asked me to say a little about the dashboard I have been working on. I saw Ed Seidel give a talk in Hannover last month and become interested in the NDS concept. Since then I have been experimenting with the idea of using the Object reuse and exchange (OAI-ORE) Web-based protocol to represent a research piece, along with the associated doc, data, code, tools, etc, as a Web aggregation. So, the general idea/hypothesis is that this model could help expose a publication collection as a single entity using a standardized method through the Web and that different serialisations of this model can be mapped using Web content negotiation (e.g. HTML, XML, JSON etc) to create different "views" e.g. a Web landing page, a Web API, a downloadable bundle, etc, depending on the query. Since ORE exposes a resource map that defines the relationships between the content, such an API can be used to discover (introspect) the web aggregation and interact with it programmatically.
To this end, I have created a pilot Website that models ORE concepts for creating and displaying research publications along with the various resources that can be included with them. It is written using Semantic UI and leverages HTML5 drag and drop to simplify the process. I would be happy to provide a URL to that site if anyone is interested in learning more, sending comments or getting involved in that aspect.
Thanks, all the best,
Ian
Hi Christine and Vishu,
Thank you! This is a great connection to make. I'm somewhat familiar
with OpenTopo (I'm sure others here are more familiar than I am
though) and it would be very interesting to learn more about how the
various pieces fit together.
-Matt
On Wed, Oct 8, 2014 at 2:03 PM, Kirkpatrick, Christine
<christine@xxxxxxxx> wrote:
Greetings, all!
Matt, you might brainstorm with SDSC’s Vishu Nandigam on EZID integration.
He has a working implementation that assigns DOI’s for one of his projects,
OpenTopo. It’s a SOA-based architecture and with any luck, we might have
pluggable code to share.
Thanks,
Christine
Christine (Bagwell) Kirkpatrick
Division Director, IT Systems & Services
San Diego Supercomputer Center
UC San Diego
Christine@xxxxxxxx
---------- Forwarded message ----------
From: "Matthew Turk" <matthewturk@xxxxxxxxx>
Date: Oct 8, 2014 11:13 AM
Subject: Ongoing architecture work
To: <discuss@xxxxxxxxxxxxxxxxxxxxxxx>
Cc:
Hi all,
A couple of us have been working on deploying at NCSA a preliminary
architecture for the NDS, based around commonly available software and
with some homegrown development as well. We've been taking notes
here:
https://docs.google.com/document/d/1SBRatAebX5-eQXB4qTFb5UGV0Cwy8Ppux_2RPs2ZUZY/edit#heading=h.b1qfdq9dlvv
(Please excuse the first person, that's all me...)
There are some action items in the document, and it's also able to be
commented on by anyone with the link, so feel free to do so. Right
now, we're trying to stand up:
* NDS Dashboard (IanT, do you want to chime in about this?)
* Analysis launching (Kacper, feel free to share about this)
* Authentication using first LDAP here at NCSA and soon InCommon
* Storage backed by disk (frontend by iRODS), cloud storage (NCSA and
SDSC, fronted by SciDrive), and access to other providers (fronted by
ownCloud)
* EZID DOI generation -- IanT has been exploring this, and we're
hoping to sync up with some folks from the UIUC library to understand
better the process and for some direct collaboration
There's some more going on as well, but I'm writing primarily to open
up what has been a somewhat insular discussion to the broader
community and to seek feedback, solicit engagement and to see where we
can take this together. We're still in the process of getting code
online, but it will be hosted at either the bitbucket or github sites,
and we're keen to get people to explore, contribute feedback or
changes, and help out with conceptualizing. Please don't take the
list above as "all inclusive"!
One principal goal is that whatever we develop is able to have new
components brought in with a minimum of fuss, components swapped out
with a similarly minimum of fuss, and that we aim to make something
that's (easily) deployable anywhere, not just at NCSA.
We're keen to get some feedback, either on the document, or here over email!
Thanks,
Matt
|