[Duraspace] Draft Agenda for Open Repositories 2013 DSpace Developers/DCAT Meeting

[Gibson, H <hgibson@sun.ac.za>]

Hi All

I agree with David. Are there any example VIVO websites to look at?
I am interested to see how VIVO and DSpace will inter-operate.
For example, can a researcher submit details about a published article to VIVO and then VIVO uses SWORD to deposit the article automatically to DSpace.

Cheers

hg

Hilton Gibson
Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

http://www.sun.ac.za/library
________________________________________
From: irtalk-bounces at lists.lib.sun.ac.za [irtalk-bounces at lists.lib.sun.ac.za] on behalf of dtpalmer [dtpalmer at hku.hk]
Sent: 01 July 2013 11:04 PM
To: dspace-general at lists.sourceforge.net; irtalk at lists.lib.sun.ac.za; duraspace at lists.lib.sun.ac.za
Cc: dtpalmer; s.moranti at cineca.it; Bollini, Andrea (a.bollini at cineca.it)
Subject: Re: [Irtalk] Draft Agenda for Open Repositories 2013 DSpace Developers/DCAT Meeting

Dear All,

Per Hilton's email below, indeed yes, I wish to see ORCID and DSpace-CRIS made core to future DSpace development.

I've been scratching my head wondering how to get more traction for DSpace-CRIS within the DSpace community.  After presenting on this topic at the ALA conference this week in Chicago, I discussed the situation with colleagues here.

Most libraries in the US run DSpace for publications of one sort or another.  Author profile initiatives such as Vivo seem to be moving to depts other than the library.  Then Vivo for author profiles and DSpace for publications will remain separate systems, managed by different depts.

However for most institutions, collecting, describing and contextualizing research objects beyond publications is still blue sky.  Most institutions have not done it yet.  It is an area that libraries, already with a publication respository, could move into very easily now in these early days.  The work we have done for DSpace-CRIS could facilitate.

Hoping for more dance partners,

David Palmer
The University of Hong Kong

From: Hilton Gibson <hilton.gibson at gmail.com>
To: "irtalk at lists.lib.sun.ac.za" <irtalk at lists.lib.sun.ac.za>,
        Duraspace <duraspace at lists.lib.sun.ac.za>
Subject: [Irtalk] Fwd: [Dspace-devel] Draft Agenda for Open
        Repositories 2013 DSpace Developers/DCAT Meeting
Message-ID:
        <CAAV1Wv40RbjrH7a9GUj0Cabo9fzkrgngQcgGs=5WzHNZqV5OHg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All

Please review the agenda.
I see the matter of researcher ID's is not on the agenda.
How do we prove to researchers the impact of openness if we cannot properly
identify them in the first place.
I think this is crucial for advocacy in the long term.
The CRIS module recently released by the HKU should be a core part of
DSpace and so should ORCID ID's.
If you agree then please send an email to:
http://lists.sourceforge.net/lists/listinfo/dspace-general requesting these
core additions to DSpace before the meeting.

Cheers

hg



________________________________

E-pos vrywaringsklousule Hierdie e-pos mag vertroulike inligting bevat en mag regtens geprivilegeerd wees en is slegs bedoel vir die persoon aan wie dit geadresseer is. Indien u nie die bedoelde ontvanger is nie, word u hiermee in kennis gestel dat u hierdie dokument geensins mag gebruik, versprei of kopieer nie. Stel ook asseblief die sender onmiddellik per telefoon in kennis en vee die e-pos uit. Die Universiteit aanvaar nie aanspreeklikheid vir enige skade, verlies of uitgawe wat voortspruit uit hierdie e-pos en/of die oopmaak van enige lêers aangeheg by hierdie e-pos nie. E-mail disclaimer This e-mail may contain confidential information and may be legally privileged and is intended only for the person to whom it is addressed. If you are not the intended recipient, you are notified that you may not use, distribute or copy this document in any manner whatsoever. Kindly also notify the sender immediately by telephone, and delete the e-mail. The University does not accept liability for any damage, loss or expense arising from this e-mail and/or accessing any files attached to this e-mail.