| Note |
|---|
This is an archived listing of project ideas for Google Summer of Code in 2009. To see which projects actually took part in GSoC 2009, please visit the Past Google DSpace Summer of Code Projects page |
| Panel | ||||||
|---|---|---|---|---|---|---|
Contents
|
...
Feel free to review previous ideas in the Google DSpace Summer of Code Ideas 2008 page, if anything seems appropriate, please feel free to bring it forward.
...
After some discussion within the DSpace 2.0 group, we've concluded that using the GSoC as a source for moving forward the DSpace 2.0 initiative is an excellent idea. If you have an idea for DSpace 2.0 development, please feel free to add it here. We will be organizing a list of ideas within the DSpace 2.0 Architecture group and presenting that list here as well. If you would like to discuss DSpace 2.0 projects explicitly, please feel free to join the dspace-architecture list as well and drop us a note there.
https://lists.sourceforge.net/lists/listinfo/dspace-architecture
- General note on code from the GSoC developers
- Code should be maintainble and adhere to the code style of the DS2 project
- Code must not use any packages with licenses which are incompatible with free open source (commercial, GPL, LGPL)
...
At present metadata collection is based on the input-forms.xml file. This file can be edited to collect different metadata for different collections. An alternative is proposed that would allow the administator to collect different metadata based on item type. There are no doubt many ways this could be achieved, for example:
- An alternative input-forms.xml file based on item type.
or..
- An admin page that would allow the administrator to select metadata terms for each item type. Sensibly this information would be held in the database rather than a file. If I understand Christophe's proposal above then this option would dovetail nicely in that the definition of data type would no longer be done in input-forms.xml.
Robin Taylor.
University of Edinburgh.
...