Panel | ||||||
---|---|---|---|---|---|---|
|
Google Summer of Code Ideas List for
...
DSpace
...
Note | ||
---|---|---|
| ||
Please add your suggestions for GSoC 2012 2015 projects related to DSpace! If you are interested in mentoring, please let us know! Also, be sure to visit the listing of Past GSoC Project Ideas below, to see if anything there is still relevant. Also, please note that Google has recommendations on what to minimally include in each "Idea", see: What is an Ideas List? NOTE: The below DSpace-specific ideas table is automatically embedded into the global DuraSpace Google Summer of Code Ideas page. |
Please add your own ideas to the table below, and feel free to volunteer as a mentor for any existing idea idea.
...
Summary
...
Relevant DSpace component(s)
...
Excerpt | |
---|---|
|
|
...
Stop Using Email as User Identifier
...
EPerson
AuthenticationManager
...
Use of email address as a persistent identifier for the DSpace conflicts with the fact that email addresses are not persistent. Email addresses go away and/or are reassigned to other individuals. There are also policy concerns with Authenticators like Shibboleth and CAS that may or may not deliver an email address as a organizational policy.
This Task is a placeholder to identify a solution to correct for the problem.
1.) DSpace should use a different identifier / key for the EPerson (netid? or combination of "authenticator + netID")
2.) DSpace should make providing an email address as optional for cases where the Authentication features lack this specific capability.
3.) Issuing emails should be optional for accounts without email addresses.
4.) Stop storing email address (or any other detail about who made the change) in dc.description.provenance field.
One proposed solution to this problem is that the Authentication Method should be broken off of EPerson and stored separately, making EPerson a "Profile" and the method of Authentication be stored separately (Password, Certificate, LDAP, Shibboleth, CAS, Facebook, Google) Different AuthenticationMethods may store the data as they see fit. And the Profile would store only those local details for that user.
See for more detail: https://jira.duraspace.org/browse/DS-937?focusedCommentId=24361#comment-24361
...
...
storage-triplestore
storage-fedora
dspace-storage
...
...
Disseminator Framework
...
ItemView
Item
Bitstream
XMLUI
A Disseminator Framework will associate Disseminators with Items and/or Bitstreams, Disseminators will combine METS file description and behavior sections to supply the user interface with a standard representation of the dissemination services that can be applied to a content bitstream in DSpace. See for further background:
|
Past Ideas Lists for
...
...
Extend Metadata Framework to Support Stronger Typing and Validation
...
MetadataValue
MetadataField
MetadataSchema
Community
Collection
Item
Bitstream
XMLUI
...
Extend the DSpace Metadata Domain Model to support the following features:
- Community, Collection and Bitstream Level Metadata
- Create "ContentType" or "Classes" Domain Model for Items and Bitstreams that define Metadata Fields that Should / Could be Present and their occurence
- Allow MetadataFields to define the appropriate Authority Controls that can be applied to them at the Domain Model level so that they can be used to inform Submission and Edit Forms (rather than using dspace.cfg properties.
- Correct Dublin Core Model and Add More default namespaces (Dublin Core Terms, ETD, VRACore and BIBO Namespaces
Research Applying METS more fully in the DSpace Domain Model - Allow Metadata "Files" that are stored in Bitstreams attached to Item but rendered in XMLUI and Descriptive, Administrative Metadata Sections
- Allow Behaviors to be attached to Fiel Descriptions, Structure Maps, etc
- Allow Structure Maps to be more descriptive of the contents of the item.
- Describe and attach Bitstream level metadata as descriptive and administrative metadata sections
- Describe and Attach Collection and or other relationships in administrative metadata sections (Similar to Fedora)
- Formalize how "Relations" Between Items should be expressed in METS metadata (see Fedora Rels-Ext for examples).
Create a Validation Service Capable of Reviewing the Metadata and Content of the Items, Create Curation Tasks that can call the Validation Service by the Repository Managers
...
...
Rewrite Packager Framework
...
dspace-api
packagers
crosswalks
...
Refactor Packagers to support Chain of Command
The packager framework in DSpace is rather rigid and unwheldy, an excellent project would refactor the Packager and Crosswalk frameworks to support more basic packagers and crosswalks. DSPace METS SIP Packages and/or SWORD packages are not the only types of packages out there. in fact, METS was never meant to be "repository specific", but to be "content specific". A better Packager Framework would gracefully degrade based on features it could detect about the incoming content being ingested, even in the METS case, DSpace should be "Profile Agnostic" and accept any METS package to derive one or more DSpace items.
...
...
DSpace Core Domain Model
...
dspace-api
dspace-services
dspace-core
...
Accessibility
...
dspace-api
dspace-xmlui
...
...
Enhance REST-API Implementation
...
REST API
...
Needs mentor(s)
...
Metadata Reconciliation with Authoritative Sources
...
EditItemStatus
EditItemMetadata
...
...
Enhancements to DSpace Statistical Reports, including one or more of the following: Develop Visualizations, tabbed/paginated inteface, and/or "Export to CSV"
...
Solr Statistics Engine
XMLUI
...
The current DSpace Solr Statistics Engine interface is rather simplistic in nature. Maybe it's time to spice it up a bit and add some better visualizations (via something like Google Charts API). It also could be worthwhile to paginate or tab the interface, both to help improve performance (less queries on one page = better performance) and so that administrators are first shown a "general summary" page, but can choose to visit other pages/tabs to get more detailed statistics in the area of interest.
- Another idea is to support "Export to CSV" for a date-range, allowing users to generate Excel reports based on statistical information.
- Related: recent Ohio State Statistical "Report Generator" improvements: Screenshot (Zoomable) & Stats Code
...
Needs mentor(s)
...
DSpace GSoC projects
We have archives of all our Past GSoC Ideas Pages still available for reference/ideas. However, you should check with the available mentors before suggesting any of these older project descriptions. In some cases these projects may require rethinking to bring them up to date.
Children Display | |||||
---|---|---|---|---|---|
|
...
|
...
|
...
Past DSpace GSoC Projects
...