Title: Message Title
|
|
|
|
1) The same curation task could be attached to a workflow step (for new submissions) and run over existing Items, Collections, etc. Doing it this way also leaves us the option of building multiple variants for different services, if they are too unlike to make a single good implementation serve all. You can plug in whichever task(s) you need, or none if you need none.
2) Offering one's repository as a source for these services sounds interesting. I think it does need to be a separate issue. But I wonder how much more DSpace needs to do, to make this work. DSpace already exposes documents for use across the network. Other than notifying a service that one's repository is available *here* and offers *these* forms of metadata, what would such a service likely want to see?
3) Taken together these two ideas seem to mesh nicely with the upcoming OR14's theme of repository as member of an ecosystem.
|
|
|
|
|
|
|
|
There are many online services that provide plagiarism checking. These services check documents against a reference database and the internet for plagiarism. I think that there should be an option to connect dspace with a plagiarism checking service so that when a user uploads a thesis or a document this document should be automatically checked for plagia...
|
|
|
|
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
