Page History

...

• Rewrite of Creative Commons licensing (MIT - ready to go) – would improve upon the features of the current CC licensing submission step
  • Currently only against XMLUI from MIT
  • Legacy problem – do we update old license to new or not? Currently MIT runs 'split version' with old licenses looking like old, and new look like new.
• Google Scholar work (MIT - ready to go) – better metadata for Google Scholar (citation tags in header).
• CGIProposal (Richard Rodgers/MIT – Interface & XML serialization implementation should be ready), based on the Item type based submission patch picked up by Robin Taylor (initially a GSoC project) – would allow for type-based submission processes (e.g. Theses/Dissertations could have different submission steps than articles/papers).
  • Context Guided Ingest – define an interface, where any submission code can write "attributes" and can retrieve those again later on. Can add any new attributes/values that you want for your submission code. Could be serialized to XML (using input-forms.xml) OR have an implementation of that service that stores in DB (recommended). JPA2?
    • seems similar to SimpleStorage Service (user centered storage of state info) – Mark Diggory.
• CurationTaskProposal (Richard Rodgers/MIT – some will be ready) – would allow for a more standard way to integrate curation tools (e.g. virus scanning, format identification, etc) into DSpace
  • Lightweight framework to attach curation tasks – 3-4 tasks for 1.7. These could be kicked off by commandline (in batch) or Admin UI (potentially)
    • 1. Automated replication
    • 2. Streamlined Checksum Checker
    • 3. Virus Checker - ClamAV (Tcp socket communication)
    • 4. ??? Better content format identification (may not be ready for 1.7)
  • Could relate to Scheduler service (Spring based) in Modules area. Allows you to register & schedule events. – Mark Diggory
• AipBackupRestorePrototype AipBackupRestore (Tim Donohue/DuraSpace) – would allow for a more complete backup of DSpace into METS-based Archival Information Packages (AIPs). These AIPs could also be used to migrate DSpace content (Communities/Collections/Items) from one system to another.
  • Refactoring Packager interface to use java.io.File instead of InputStreams – would require refactoring of SWORD & LNI.
  • May require using a Temp folder to cache streams.
  • Eventual goal to separate out Packagers & Crosswalks to a separate API – may not be ready for 1.7
• SWORD Client for DSpace? (Robin Taylor – may be ready, Richard Jones & Stuart Lewis are interested in helping) – would allow DSpace to push/submit content to other SWORD enabled repositories
  • For closed & open access repositories – add a button to transfer content from a closed to an open repository.
• Discovery work, potentially?
• Possibly one or more of the Google Summer of Code 2010 projects (if they are ready/stable enough for release)

...