> Huh? What is this good for? What is wrong with the existing > importer?
The importer itself seems to work fine. Its the DSpace web forms that lack the customization and flexibility that we need. And implementing a direct import from my own web forms would be prettier than saving the collected data on server and then running it through importer. > Why not enhancing it if you are missing some > functionality? Why mix in another technology? Well thats an option, but since the development of PHP applications is much faster than with Java and we already have an existing architechture built on it, it presents itself as a tempting option. > PHP tends to require a serious adinistrative overhead for security > updates every other week or so. Somewhat true, but so far, we've managed to update the system painlessly every time it has been relevant. And like said, since we already have working PHP applications, it has to be done anyway. > When talking about web forms, authorization is another issue. How to > integrate > with existing account system in DSpace. I dont see it that way. One could use a pre-defined administrator/submitter account to do the actual upload and have the web form log the actual user info (if needed). Via LDAP University's user accounts can easily be fetched or the forms can be placed under restricted IP's or relevant subnets. So its actually not that big of a problem. To me DSpace's restrictions in customizing the input-forms presents a bigger issue. -Mika ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
