Thank you for that analysis. Interesting. Much of the stuff they are pushing into IR+ is stuff I would like to see pushed *out* of DSpace.
On Wed, Jan 27, 2010 at 11:05:28AM +0100, Bram Luyten wrote [in part]: > Elaborated user account settings > > - Multiple Email Addresses > - Publication Name Management (especially useful when you get married > during the course of your academic career) > - An overview of accepted licences The last is properly part of DSpace, I think. The rest shouldn't be part of any customer-facing product; those are functions of the enterprise directory service (when there is one) and DSpace should just ask the directory for what it needs when it is queried, returning as many results as it got, and letting the directory make decisions about who gets to see telephone numbers (for example). A customer-facing product of course needs a very basic identity subsystem plugin for use when no enterprise service is available, but it should be held to the features required to support the product's own functioning: authentication and access control. If you want fancy, get something that was made for doing fancy and plug it in. Identity management is not one of DSpace's core functions and shouldn't grow to overshadow those operations which *are* its core functions. Rather we should be a very good client of identity management services. > Researcher Pages > > - File & Link association > - Pictures > > The researcher pages offer nice "profile" functionality, which is way better > than currently offered in DSpace, but way lagging behind the current state > of the art in this field (Facebook, Linkedin, ResearchGate, ...). Social > features on the Researcher pages are lacking (colleague list, comments, > ...), as well as integration of external services (blogs, twitter feed, ...) Well, another way to look at this is as an alternative view over the metadata base. That we should do -- we need to address the needs of contributors, and aggregating their work is one thing they seem to like. :-) BTW how about exporting aggregated machine-readable bibliographic information, while we are pulling this view together? Would contributors ever find that useful? The rest sounds like a portal. Instead of turning DSpace into a portal, shouldn't we work to ensure that it is easily plugged into things whose function is to be portals? So, if it were easy to request machine-readable information on assets selected by author...what do we have in that line? what *should* we have? > User Workspace > > - File and Folder Management > - Share files with other users > - Version management: upload new versions for files > - File locks & Permission mechanism > > The implementation of User Workspaces gave me a very Google-Docs like > feeling, but without the in-browser editors. Uploading & downloading files, > and managing them locally on a PC could possibly be a show stopper here. But > the version management, permission & locks and sharing system seem well > implemented. Can't we find a well-made workflow system already existing, and fit it in? (Or fit DSpace into it. Again, this is something that applies across various repositories, not all of which will be DSpace.) > Submission > > - Multiple collection selection for one submission > - File(s) selection first > - Collection(s) selection last > > As opposed to the DSpace submission process, IR+ starts from the file > upload, and adds metadata provision afterwards. This would be useful in any > approach where some metadata could be automatically generated from the > uploaded file. The metadata-first approach does have the advantage that file upload serves as a reward for slogging through the paperwork. But submissions do have to be accepted, so we don't really need to say, "no uploading until you've finished your metadata!" Just send it back with a note on what's holding up publication. Upload-first with automatic metadata extraction would OTOH be a reward to encourage people to use the metadata features of their authoring tools, which are little used now. > The software could be used to implement both a repository, as well as a > referratory: it's possible to add a new "publication" without adding a file, > but adding a hyperlink to an external resource instead. Hmmm. I've been muttering for some time that people shouldn't necessarily be coming directly to repositories to look stuff up; aggregating search tools should be farming out queries to multiple repositories, arranging and presenting what they get back. No, I don't mean Google; I mean serious, powerful (as opposed to fast) search/presentation tools. I guess the common theme of my remarks here is that of seeking success through intelligent interdependence. Other services give DSpace more accessibility and connectedness, while DSpace gives them access to more well-described information content. -- Mark H. Wood, Lead System Programmer [email protected] Friends don't let friends publish revisable-form documents.
pgpPT9T4KsMXk.pgp
Description: PGP signature
------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
_______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
