@electronic{www.uic.edu, title = {Scientometrics 2.0 Toward new metrics of scholarly impact on the social web}, url = {http://www.uic.edu/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2874/2570}, biburl = {https://puma.uni-kassel.de/url/5fcb0c866b481988e6f82d16e5b6efe0/stephandoerfel}, keywords = {citation elsevier evaluation index item quality recommender research scientometrics toRead}, added-at = {2012-03-09T14:45:54.000+0100}, description = {}, interhash = {5fcb0c866b481988e6f82d16e5b6efe0}, intrahash = {5fcb0c866b481988e6f82d16e5b6efe0} } @electronic{www.mail-archive.com, title = {Re: [Dspace-tech] SWORD: Polling for Handle Availibility When a"accept/r}, url = {http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg07979.html}, biburl = {https://puma.uni-kassel.de/url/879f5cfc04b126271829019cb4001691/stefani}, keywords = {handle item mediaLink puma submit sword}, added-at = {2011-01-14T15:55:00.000+0100}, description = {Unfortunately you have hit one of the limitations with the current DSpace SWORD implementations. Due to the way DSpace currently works, it does not generate an item handle until the item has completed its journey through the workflow(s). And to compound this problem, the media link will not return anything for items that are due to go through a workflow. It is probably worth submitting this as a bug in JIRA (jira.dspace.org) so that we can assess it for future releases. The first of these issues (and therefore the second too) may get fixed in 1.6 if we can find the effort required to port some previous work on the identifier system to 1.6 to ensure that all items are given item identifiers. If this work does not get incoroporated in 1.6, we could look at adding a new DSpace table to associate a new SWORD deposit ID with the final ID and return that to the user via the media link. }, interhash = {879f5cfc04b126271829019cb4001691}, intrahash = {879f5cfc04b126271829019cb4001691} }