Review of New Issues
In JIRA:
- FCREPO-496: Permgen grows when Fedora is repeatedly deployed/undeployed w/o restarting Tomcat (GrahamT)
- FCREPO-426: Revisiting "managed external" datastreams (RonJ, orig proposed by MatthiasR)
- FCREPO-497: DS title as content-disposition filename when GETting datastreams from Fedora (MattZ)
- Related: dates in URLs
- Also: extensions with IE
- Or: Preferred filename
- NSDL uses as filename (so does stanford)
- FCREPO-498: Connection pooling via c3p0 -- dbcp out of date (AaronZ)
- FCREPO-445: Cardinality support for DS-COMPOSITE-MODEL (RichardG)
- FCREPO-499: Validation on ingest (AndrewW)
- Folks working at Goddard, simple case of XML, want schema validation on ingest
- FCREPO-500: (related: FCREPO-405) Support for PUT/POST/DELETE on disseminators (MatthiasR)
- FCREPO-501: Fedora as WAR without need to run installer (Asger, TimD, etc)
- Need more detailed discussion on this (long-term strategy)
To-be-entered:
- WebAdmin ability to change configuration on the fly
- Update docs to indicate that the preferred file upload method (for add/modify datastreams) is via the REST API rather than upload servlet (MattZ)
- Upload vs "by reference" and temp files
- Support for hierarchical storage (new verb that says, asking if the datastream is available), Dan: heard from Sun, Donna Harland, also Matthias, Juan Rodruigez, also someone from U of Minn. also Multiplexing Eddie: Heard from Stanford person re:hierarchical storage. Did their own abstraction layer. Alpana Pande? Lazy Susan.
Debrief of OR09
What did we hear
- Request for blogging of DuraCloud activities (MattZ, others)
- Action: Add DuraCloud wiki space
- Request for Fedora transparency
- Interest in Special Topics meetings
- Interest in recording audio of meetings for people to listen to later
- Action: June 9th for Special Topics
- Request for details of FedoraRepository/DSpace architectural roadmap
- ...
Potential actions
- Draft release of 3.3 feature list
- Promote feature "interest groups"
- These groups would ideally be self-forming
- May need initial help from core-developers to establish precedence
- Would have wiki area for design, units-of-work, status, etc...
- maven2 ?
- fedora as self-contained, deployable war ?
- OSGi ?
- Web Admin additions ?
- Enhanced Content Model ?
- Workflow ?
- Security redesign ?
- ...
- New development infrastructure
- OSUOSL for hosting svn, etc...
- Forum
- Mailing lists
Establish "contrib" area of svn Plan towards "garage sale" - Want latest Roadmap on website/wiki (TimD discussion: "Roadmap" theme as Jira field, and auto-generate parts of roadmap from Jira?)
- Maven2:
- Lots of positive responses
- MarkD wants Fedora POM for DSpace-on-Fedora builds
- OSGi:
- DSpace considered OSGi early on, but steered away from it in part due to percieved complexity. Currently using it's own "OSGi-like" module approach, using Spring.
- Sakai went back and forth on OSGi, now moving toward it.
- AaronZ (sakai/dspace2 committer) gave us an osgi primer
- DaveF pulling together resources for Eddie+AaronZ to go to osgi conference and experiment with OSGi-fying Fedora
- FedoraFS (Rebecca Koeser@Emory's repo challenge entry):
- Allows use of Fedora via standard filesystem interface (video here)
- ChrisW talking w/Rebecca this week: re: potential "contrib" project
- Wider developer participation:
- Sakai experiences:
- When voting on issues, people tend to choose the big, difficult items.
- Having a "contrib" area has been very successful
- Sakai suggestions:
- Put out a list of things to do; people will help (even if not right away)
- Get people helping in non-coding ways (docs, managing users)
- Make sure people and institutions get proper credit for their contribs
- Sakai experiences:
- Desire for dev-focused get-together
- Somebody did a Fedora Ubuntu/Debian installer (poster)
- Fedora integration with JPEG 2000 (http://apps.sourceforge.net/mediawiki/djatoka/index.php?title=Fedora_Integration)
- Bill Parod interested in being able to allow only certain API-A methods to be accessed by unauthenticated users