We've been working with some interested groups, in order to get CAREO "out there," and I'm just trying to get a better handle on what our potential end-user institutions need from a repository server.
UPDATE: Please provide feedback on this, even (especially?) if you agree with the assumptions. Clarity is a Good Thing.
Here's the assumptions we've been working under. Institutions will need to (in no particular order):
- Host their own instance of the repository (or have it hosted by another group)
- Customize the interface of their instance to match their online identity
- Some groups will want access to source code in order to modify/add functionality, but most groups will want a turn-key solution similar to an off-the-shelf software package
- Those folks that want to hack on the code will be able to speak Java fluently (technically and/or philosophically
- Standards are important. Support standards wherever possible/appropriate (both visibly and behind the scenes).
- The exact technology used won't matter a huge amount, as long as it works (well).
Do potential partners have different needs from what we've assumed? I don't know. If you have something you'd like to see, please let me know (either by email, or in the comments for this post).
UPDATE 2: So far, I've only received a single response to this question (via email). I'll have to assume that means 1 of a few things:
- People agree with these assumptions
- People are too busy to respond at the moment
- These assumptions aren't important/relevant to what potential users are looking for
I'm hoping it's just the second one...