On Tue, Dec 03, 2013 at 12:01:32PM +0800, lei chen wrote: > I am new to Dspace and have very limited IT knowledge. > Recently my institute decided to develop a online archive to store > papers/reports produced, Dspace was suggested. > Beside the uploading, searching and downloading function, we have extra > requirement from management team: > 1. more detailed personal information(work, edu,geo location etc), different > level of authorization, supervisor- supervisee interaction (and supervisor > have the authority to access/edit supervisees' work docu, ). > 2. statistic module to retrieve summary of personnel, papers/reports > 3. integrating the electronic calendar(already exist) to online archive, > allow users upload and download event related documents. > > After some reading, I am trying to wrote my first plan, here come's my > question: > A: Use Dspace as it is, and construct another database to store extra data > needed(personnel,work relation), and build a API to communicate between > Dspace and new database. > B: Modify Dspace's tables and use its database, write extra codes to execute > function needed > C: use some other software other than Dspace. > > When we have only one PHP/Mysql programmer in our team, which way should be > the most feasible and easy.
I would first look around the institution to see what other sources of personal information are available. If your personnel records are kept in electronic form, you might be able to connect to them with little effort. Directory services are designed for such things, and DSpace already can use LDAP to connect to a directory service. I would be wary of importing personnel-management functions into DSpace or any similar document archival product. I'd say it is much better to fetch what information you need from management-support systems that you already need for other purposes. I would consider the use of the REST interface to be released with DSpace 4.0 to support external statistical reporting tools. Rather than create a lot of statistical reporting code, I would first try to extract the needed raw cases and process them with an established statistical package such as SPSS, SAS, or R. Again, you may already have those tools, and people who know how to use them. I feel that I don't sufficiently understand your third requirement (about event-releated documents) to offer advice. To modify DSpace's business logic, your programmer would need to develop some skill with Java. To modify the user interfaces would require Java and JSP skills, or XSL-T and perhaps Java, depending on whether you selected JSPUI or XMLUI. DSpace is not supported on MySQL, but database skills should be transferrable to PostgreSQL or Oracle (the supported DBMSs) with a small amount of effort. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
