Details
-
Type:
Rice Enhancement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Unspecified Future Release
-
Labels:None
-
Rice Theme:Industry Standards
-
Priority Score:0
-
Functional Justification :
-
Impact if not Implemented:Implementations will continue to be a labor intensive affiar and applications will need to create their own leading to inconsistencies across Kuali applications and duplication of effort.
-
Priority - KFS:Critical
-
Priority - KC:No Priority
-
Priority - KS:No Priority
-
Priority - Rice:No Priority
-
Theme:Kuali Application Business Drivers
-
Effort Estimate:Medium ~ 500 hrs
Description
Several institutions require integration of their document management system (DMS) with the Kuali applications. Support in Rice would make this integration
consistent and easier to implement.
See https://test.kuali.org/confluence/display/KFSIMP/Kuali+-+EDMS+Integration
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is relied upon by
-
-
- Rice Roadblock
-
- relates to
-
-
- Rice Roadblock
-
- Trackbacks
-
![[Confluence: Kuali Rice]](/images/icons/generic_link_16.png "[Confluence: Kuali Rice]")
Copy of Roadmap Draft 2 - Hampton
Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
-
Kuali Rice Roadmap 2011
Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.1, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Kuali Rice Roadmap 2012
Draft Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.2, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Rice 2.3 Design and Analysis
Milestones and Timelines Teams Structure Team KRAD Jerry (DM) Brian Samuel Red Team Claus (DM) Steve Jeff Corey Blue Team Peter (DM) Martin Sona Shannon QA Team Erik Mayank Viral Shared...
-
Rice 2.3 Project Plan
DRAFT roadmap not finalized yet Overview Timeline: Proposed 9 month release (\ 1/15/139/15/13) Split: 68% new features/32% maintenance Roadmap Items # KRRM144 https://jira.kuali....
-
Roadmap Draft 2
Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
Activity
UC Berkeley's Research Administration and Compliance is using Alfresco, and we would like to integrate with Kuali Coeus.
UC San Diego is also interested in integrating Kuali Coeus with Alfresco for electronic document management.
KFS is interested in this. I had volunteered to be listed as the champion for KFS. Diane, if you would like for me to do that, please re-assign. Thanks,Kymber
KFS has in interest in this so Kymber has volunteered to champion.
Some of you may be aware that Kuali OLE has integrated Apache Jackrabbit Content Repository technology in to manage arbitrary documents related to descriptive metadata, licensing, communications, and localization of information. This technology already has a CRUD interface on Rice.
Wanted to make everyone aware that Kuali Student released as part of it's Curriculum Management a service contract interface for managing uploading and attaching documents. We released the a basic implementation but the assumption is that schools would map their "real" (often commercial) document management system to that interface and all would work.
From
KRRM-29: Provide integration capabilities into other open source and vendor document imaging and management systems. Cornell has expressed interest in integrating with it's Fedora Commons (Duraspace) system. UW has ImageNow vendor product. UA uses DocuWare and is looking at OnBase.