Date & Time

  • April 12th 15:00 UTC/GMT - 11:00 EDT

Dial-in

We will use the international conference call dial-in. Please follow directions below.

  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free: http://www.readytalk.com/intl 
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
    • Once on the call, enter participant code 2257295

Agenda

Open Discussion

Update on Open Repositories Dublin 2016

 

Preparing for the call

Bring your questions or topics you would like to discuss to the call, or add them to the comments of this meeting page.

If you can join the call, or are willing to comment on the topics submitted via the meeting page, please add your name, institution, and repository URL to the Call Attendees section below.

Meeting notes

DCAT is the DSpace Community Advisory Team. We will use the full name as well as the acronym in future announcements.

 

Call Attendees

  • Bram Luyten - @mire
  • Ignace Deroost - @mire
  • Maureen Walsh - Ohio State University
  • Emilio Lorenzo - Arvo Consultores
  • Mike Marttila - Georgetown University
  • Felicity Dykas - University of Missouri–Columbia
  • Terrence W Brady - Georgetown University
  • Luiz Claudio Santos - Inter-american Development Bank

  • Leila Sterman - Montana State University

  • Vika Zafrin - Boston University
  • Pauline Ward - University of Edinburgh
  • No labels

15 Comments

  1. Request a copy: uses and feature requests

    Would be interested to hear if anyone else is relying on request a copy, and if there are any specific feature requests. Two things come to mind:

    • Reporting: how popular is the feature, and can we aggregate request counts over items, collections, communities?
    • Files are delivered via email - issues when files get too large to be delivered over email

     

  2. Regarding request copy I think is quite popular, aproximately half the repositories we deal with, have implemented the feature

    Yes, some files are blocked by the email settings due to large file size. So we implemented a solution to send a token with a link to download the file (avoiding permissions restrictions, of course) . The token has a configurable expiration date and has a limited number of uses (also configurable, usually one download)   We can share the code, or report a JIRA and a pull-request or....This solution is working in a couple of repositories: v1.8 xmlui and v5 xmlui

    Just for documentation purpouses, also we have a request of limiting the number of electronic copies an author can send.... I know is a quite bizarre request, probably inherited of times when editors provide "n" editor-copies to authors..  We have not implemented any solution about this request

     

  3. Can't get through on the phone for some reason, even though I'm dialling the usual number as stored in my skype, and have double-checked the info on the meeting wiki page is unchanged.

    1. Pauline, I am sorry I am not sure what the problem might be. We are using the same number.

      1. OK thank you, not to worry. I didn't have any burning issues to raise today anyway.

        1. I finally got through. Dunno what I did different, but just worked this time.

  4. Direct link to the DSpace XMLUI test plan:

    bit.ly/xmlui-test-plan => anyone can view the test plan, anyone can also apply for edit rights to enter test feedback content.

    More information:

    2016 DSpace 6 Testathon Testplan Working group

    1. Thanks Bram. ASKOSI  is the vocabulary server I was talking.

      The other one is https://sourceforge.net/projects/tematres/    tematres controlled vocabulary server

  5. The link to the video on controlled-vocabulary flavours (sorry,  the titles are in spanish)   

     

    first, an example on Unesco Science & Technology voc. (200 terms?)   

    second, the  European Education Thesauro,   4000 terms?    

    third is ASFA (Agriculture......) perhaps 10K-20K terms     

  6. Google Search Console (Google Webmasters) – It is interesting tool to help you to see how Google search your repository. They have some report that bring numbers of clicks, impressions and average position of the repository in Google.  

    https://www.google.com/webmasters/#?modal_active=none

     

  7. Similar to what Terry mentioned on the call about aggregating statistics across collections and communities, we offer a commercially licensed add-on, our Content and Usage Analysis module that can do this as well. You can see the latest version in action at:

    https://atmire.com/preview/