Huh!  That’s quite interesting.  It’s ordervalues for the access dataset (which is kindof like the apache log and tracks whenever anyone looks at an abstract page or downloads a fulltext item).  It’s unlikely that the data is of any practical use, as I don’t believe there are front-end interfaces for the access table.  It’s used for download statistics, but is processed first…

 

 

Hi All,

 

Our DBA has noticed a table that hasn’t had anything occur to it in quite a while… and I can’t see any reason it would actually be required (nor how it was created in the past, as the access dataset doesn’t require ‘order values’.  Only thing I can come up with is it was used in earlier versions, 2.3.13?? maybe 3.1.0?? and it didn’t get cleaned up when moving to 3.3.10.

 

 

Has anyone got any ideas? And/Or is it safe to remove it permanently?

 

 

Cheers

 

Matt.

_____________________________________________________________

This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.

The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider of education with the Australian Government.

(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )