Christophe, you bring up a very good point about having more involvement 
from the repository managers in the development process and reminding 
the community of what was discussed in Gothenburg.

In terms of what has happened since last fall, the DSpace Global 
Outreach Committee 
(http://wiki.dspace.org/index.php/DSpace_Global_Outreach_Cmte) has 
agreed that one of its priorities for 2010 would be to work on ways for 
the repository managers and developers to partner more together on 
development efforts.  You'll also remember that one of the specific 
suggestions was to encourage more repository managers to get involved by 
having the next release manager (or co-release manager) be someone who 
wasn't a committer/developer. This idea may or may not prove effective 
at pulling more repository managers into the development process -- but 
it certainly sounded like the committers/developers would welcome the 
chance to try it. Certainly the DGOC efforts and a the idea of a 
repository manager serving as a release manager should not be the limit 
of more community involvement, however. And I agree with Tim that this 
is a great time for the community to give some thought to "where DSpace 
sits in the IR space".  Are there some ideas of how the DuraSpace 
organization might best help provide a framework for this exchange? Is 
it a series of virtual discussions/meetings or surveys? For those 
repository managers out there, what would be the most effective way of 
capturing your opinions and soliciting your help on such a project?

Valorie Hollister
Director of Community Development, DSpace Project
DuraSpace
vhollis...@duraspace.org
Skype: vhollister


Christophe Dupriez wrote:
> Hi Tim!
>
> Here I would remind that, in Göteborg, Repository Managers told us that 
> they should drive the specs (at the very least the needs assesment).
>
> Any committee has been set up? Who follows up this committee at DSpace 
> organization? When will be some reports to developpers community?
>
> The response is propably "NO" to all these questions because Repository 
> Managers are seing DSpace as a product like another, so they just want 
> to switch if another product seems better.
> They do not want to invest more than the strict efforts and money needed 
> for cosmetic customization.
>
> Not like the developper who invests him/herself in building a deep 
> understanding of a given software to be efficient to adapt it to 
> Repository Managers needs...
>
> Am I wrong?  I hope somebody will demonstrate that I am really by taking 
> the need assesment of Institutions on his/her shoulders.
>
> Most of us work (directly or indirectly) for academic institutions 
> fighting to be amongst the most recognized in the world.
> The real problem being the general incapacity to achieve good 
> repositories, the real mission of DSpace is to provide something to make 
> those institutions succeed.
>
> If we can make those institutions aware of the upmost importance to 
> collaborate to build a common repository framework and best practices 
> specification/evaluation network, then we will have really succeeded.
>
> As computer scientists, we should not forget that DSpace was designed as 
> a "just enough" product and it succeeded because of that.
> So what is really "just enough" now???
>
> Have a nice evening!
>
> Christophe
>
>
> Tim Donohue a écrit :
>   
>> Here's another spin on this topic.
>>
>> First off, I'd like to thank Bram for doing this analysis.  I think it's 
>> extremely beneficial for us all to take a step back every now and then, 
>> look at the broader picture, and especially take a close look at similar 
>> systems to see what we can learn from them.
>>
>> Something that is also worth noting is that the folks who made IR+ used 
>> to use DSpace.  I think it's important to reflect on why they chose to 
>> build a different system, and what features they specifically added that 
>> either (a) were/are not available out-of-the-box in DSpace or (b) DSpace 
>> couldn't provide via integrations with complimentary systems/services.
>>
>> I think in this discussion, Mark Wood and Graham Triggs bring up some 
>> valid implementation questions.  It's good to question whether DSpace 
>> should try and build in some of these feature, or alternatively 
>> integrate with other external systems/software which may better provide 
>> these features.  I feel it all comes back to whether we all feel DSpace 
>> should be the "one IR to rule them all", or whether it should better 
>> "plug into" a set of complimentary services at your institution or 
>> library.  I'll admit, the IR as just a piece in a "set of scholarly 
>> services" is something that has stuck with me from having worked 
>> alongside Sarah Shreeves at U of Illinois (she has been talking about 
>> and developing this idea for several years now).
>>
>> So, I don't necessarily feel that DSpace should strive to be more like 
>> IR+ (or any other system for that matter). But I do feel we can learn 
>> from the great new features they've implemented (kudos to them!).  It's 
>> as good a point as any to step back and analyze where DSpace sits in the 
>> "IR space".  Perhaps even analyze whether there are core features DSpace 
>> is still missing, or whether more "hooks" into external systems could 
>> help DSpace become an integral piece in a set of scholarly services at 
>> your institution.
>>
>> I don't have any answers here. :)  But, I'd love to hear others 
>> thoughts/ideas in this discussion.  In my mind, DSpace is really 
>> Community Software, so ideas/thoughts/brainstorms/visions from those in 
>> the community (i.e. you) help shape our future direction.
>>
>> As we all know, DSpace 1.6 is just around the corner (still on track for 
>> a mid-Feb release).  But, that doesn't mean we cannot already start 
>> brainstorming for 1.7 (and beyond).
>>
>> - Tim
>>
>> ------------------------------------------------------------------------------
>> The Planet: dedicated and managed hosting, cloud storage, colocation
>> Stay online with enterprise data centers and the best network in the business
>> Choose flexible plans and management services without long-term contracts
>> Personal 24x7 support from experience hosting pros just a phone call away.
>> http://p.sf.net/sfu/theplanet-com
>> _______________________________________________
>> Dspace-general mailing list
>> Dspace-general@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-general
>>
>>
>>   
>>     
>
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Dspace-general mailing list
> Dspace-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-general
>   

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general

Reply via email to