Hi James,

If you are interacting with a third party application then this may explain the large number of "empty" eprint IDs.  With just human user it is possible you will still get a few of these where a user goes to create a record and then never gets round to entering any metadata.  They may then at some point go round and delete all their "empty" eprint records to tidy things up.  However, the automated creation by a third party app seems more likely.  You should get the userid and actor for these history records to see if you can see a pattern.

Regards

David Newman

On 24/08/2020 16:02, James Kerwin via Eprints-tech wrote:

Should I be concerned about the number of "empty" eprint IDs I see in the history table?

It appears there are a lot that have two instances of "revision = 1" where the record appears to be briefly created and then immediately destroyed and the relevant ID is skipped over and never used. I am making sure that I only look for "datasetid = eprint".

I don't want to get too bogged down with this because it's not the end of the world, but I am tempted to pull on the thread and see what's going on.

Thanks,

James

On Mon, Aug 24, 2020 at 2:41 PM James Kerwin via Eprints-tech <eprints-tech@ecs.soton.ac.uk> wrote:

Ahhhh that's it! Thank you!

I'm now slightly embarrassed to say how long I spent searching through the various EPrints tables looking for this.

The initial plan is to have a script that looks at how many items are put in the repository and breaks them down by some time period (e.g. month). If it's still wanted I'll make it into a button on the admin side that provides either a spreadsheet/google docs link or maybe even use it as an opportunity to play with graph modules etc.

We did look into something similar last year where we get the upload date and proper deposit date (as defined by EPrints) to assess how long items spent in review. This felt a little bit too much like surveilling staff which isn't something I'm on board with so it was quickly dropped. "Do no evil..." and so on.

Thanks,

James

On Mon, Aug 24, 2020 at 2:08 PM John Salter <J.Salter@leeds.ac.uk> wrote:

Hi James,
The 'history' dataset is your friend here!

Are you wanting to do this for a handful of records, or script something?

 

A dataset search along these lines should work:
dataset: history

datasetid: eprint

dataobjid: the eprint id you are interested in

action: 'create'

 

The history dataset is searchable via the web interface, but for some older versions or EPrints you might want to add the 'datasetid' to the search form.

 

Let me know if you need more info!

Cheers,

John

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of James Kerwin via Eprints-tech
Sent: 24 August 2020 13:43
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Date Record Created

 

Afternoon All,

 

In the EPrints database is there data on when a record was created? We have the date an item is deposited which indicates when an item was made live in the repository. The record is created prior to this when a user uploads a file or OA Link through Elements. The record is created in the review buffer.

 

When a record is modified there is a "last mod" date and when it goes into the live archive this is treated as the deposit date.

 

If not I can find a way to make it happen in future. It would be incredibly helpful if I didn't need to do this.

 

Thanks,

James

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/

Virus-free. www.avg.com