REFCC

[Jennifer Smith]

HI All

 

Apologies as I’m not very active on this list… 

 

Are there any plans (or am I behind the times) for REFCC to indicate as part of compliance checking:

 

• File(s) is (are) TDM-able

 

• Data/File(s) has (have) been harvested by CORE (some sort of feedback)

 

I understand that CORE may only pick up first file it sees

 

Also in cases where we remove from public view or delete we have to remember to go into CORE and do something there (tho files may be out in the wild elsewhere)

 

 

Would this be possible I wonder?

 

Thanks

Jennifer

 

 

Jennifer Smith | Research Publications Librarian

Information Services

St George’s, University of London

Cranmer Terrace | Tooting | London | SW17 0RE

+44 (0)20 8725 5393

 

Library Services for Researchers

 

Twitter: @sgullibrary

 

St George’s, University of London: improving health for over 250 years

sgul.ac.uk

 

[Rory McNicholl]

Hi Jennifer,

These sound like sensible additions to the things that the ref cc can check.

I've recently started a GitHub debate on plan S. Maybe an issue or two for additional ref cc features would stimulate debate between the community devs on this.

>I understand that CORE may only pick up first file it sees

 It is more that the rioxx standard (that CORE uses) only allows for a single document to be presented. There are some heuristics in the rioxx plugin to select the "best" document... But the upshot is that CORE only has one doc per repo record.

Rory

--
You received this message because you are subscribed to the Google Groups "EPrints UK User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eprints-uk-user-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/eprints-uk-user-group/LO2P265MB05925A4F1C5023574B4E2C698F040%40LO2P265MB0592.GBRP265.PROD.OUTLOOK.COM.