Re: [Myexperiment-discuss] New user data: how?

[Linde, A.E.]

I’ve certainly argued for some time that myExperiment might implement its tabs (Workflows, Files, Packs) as plugin architecture so that it might be extended by those who want to use myExperiment in other domains.

If, however, by plugins you meant something else, can you expand on this and indicate how it is or might be implemented in myExperiment?

By ‘procedural’ I was referring more to some sort of subversion and/or db:migrate process that would allow a parallel set of database changes to be kept in sync with the core ones. But any other procedural solution would be fine.

As for the extra fields, key/value pairs is fine.

The Spacebook extension to myExperiment that I’m working on does in fact implement a triplestore as the means of storing its annotations but I found it too difficult to integrate that with the existing codebase so it is all implemented external to myExperiment with additions being made by _javascript_. If triplestore access could be easily integrated with myExperiment, I’d be intersted in looking into it.

Cheers,
Tony.


On 19/02/2009 10:37, "Danius Michaelides" <address@hidden> wrote:

> Your 'procedural' solution seems to be inline with RoR's facilities to
> extend functionality via plugins.
>
> As for the 3rd party field, that seems to add alot of overhead having to
> parse out data all the time. Plus you'd have to make sure every extension
> uses the 3rd party field the same way.
>
> I think I'd prefer a solution that allows you to associate key value
> pairs with items. This could either be directly on database entries,
> or extended further by storing triples in a dedicated table, or just
> use a full-blown triplestore (with the added benefit that you're 'app'
> data could be more structured). Biocatalogues annotation system is
> related/relevant here.


-- 
Tony Linde
Project Manager
Department of Physics & Astronomy
University of Leicester