Larry Stone wrote: >> I know this topic has been touched upon briefly in past >> discussions, but >> I'm wondering if the DSpace Community has any >> suggestions/recommendations on how we can best *share* custom-built, >> *production-quality* DSpace Modules that have not been fully accepted >> into a DSpace release. >> > > I think it would be helpful to have a central directory or registry, > just to announce the > existence of each extension and point to where there is more > information about it. > This directory would be mentioned in the documentation and on the > front page of the > wiki so it's hard to miss. > > One way to do this is with a wiki category: give every module a wiki > page belonging to a category e.g. "PublicModule" and let the category > summary page be the directory. (I'm not saying the wiki is the best > tool for the job, it just happens to be available and familiar.) > > There are different kinds of modules and extensions that have > different packaging requirements. For example, a plugin > implementation that can be cleanly added could just point to its home > source code repository or SourceForge project. > > I ran into this problem too and just put a page up on the wiki with > source attached: > http://wiki.dspace.org/index.php/DSpace_SIP_Toolkit > It's a snippet of useful code, there ought to be a place to advertise > it to the community more effectively. > > -- Larry > A number of open source content management systems provide modules and extensions in categorized hierarchies making it easy to browse and search for 3rd party software.
I notice that DSpace uses Joomla! for its main site and wonder if it is worth investigating setting up something similar to extensions.joomla.org, where developers can host information about their projects and DSpace users can browse, download and comment on the addons on offer. > >> I know we have an SVN "sandbox" area on GoogleCode. But, in >> general it >> does not seem to support easily finding/searching these modules, other >> than maybe adding a page to the DSpace Wiki to find them. In >> addition, >> it's unclear if these sandbox modules are also available via Maven >> Central Repository (they don't seem to be), which would be more ideal >> for production-quality modules. >> >> A part of me even wonders whether the "sandbox" is the most >> appropriate >> place for production-quality modules (rather than the >> proof-of-concept/prototypes that usually appear there). >> >> I'm asking all this because I now have three production-quality custom >> DSpace 1.5.1 Maven modules which I'd like to make available more >> widely >> and allow others the opportunity to use, modify & help support: >> >> (1) Maven module for Delegated Administration (Community Admins, >> etc.) - >> Based on Andrea Bollini's patch with updated bug fixes, etc. [WARNING: >> Overrides some classes in dspace-api] >> >> (2) Maven module for basic Embargo/Access Restriction functionality - >> Based partially on U Michigan's embargo patch, with extra features, >> bug >> fixes, etc. [WARNING: Overrides some classes in dspace-api] >> >> (3) Maven module for basic Download Statistics - Based partially on >> old >> stats code (2-3 years old) from U of Rochester, and updated/migrated >> through the years...these stats are entirely DB driven and >> currently do >> not parse DSpace log files >> >> All three of these modules are now in production in our local >> repository >> (IDEALS): http://www.ideals.uiuc.edu/ They are all standalone Maven >> projects which work with DSpace 1.5.1 (XMLUI only at this time). I'd >> like to figure out the best way to make these available to the >> community >> at large. >> >> Suggestions from fellow developers/community members welcome! Is the >> sandbox the most appropriate place for these addons? Or is there >> another area where we should start to make space for more "mature" >> addons? >> >> - Tim >> >> >> -- >> Tim Donohue >> Research Programmer, IDEALS >> http://www.ideals.uiuc.edu/ >> University of Illinois >> [email protected] | (217) 333-4648 >> >> ---------------------------------------------------------------------- >> -------- >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) >> are >> powering Web 2.0 with engaging, cross-platform capabilities. >> Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based >> development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Dspace-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-devel >> > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Dspace-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-devel > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
