Well, off the top of my head we have:

 

Field definitions in the Perl

Some plugin stuff, third party but that must have added some tables in

The biggest one is some alterations to the user table as well as the addition of a new table for users which no longer exist on our Active Directory – there is a bunch of non-standard functions to go with these. I’m not sure if the database definition was made through the perl code or if the database structure was directly updated. The main issue here is that the code that runs this is baked into the EPrints core – the last time EPrints updated itself (admittedly from an unscheduled package update) it wiped out the code here and left us with a broken repository.

 

The purpose of this exercise is really to strip a lot of this back and decide as we rebuild what we need from the makeup of our current repository. I’d like to handle the AD logins in a less destructive way (at present there is a cron job which wipes the user table nightly and repopulates it) as well as stripping back any plugins we have running and making some workflow optimisations. Ideally I want to make sure the system is as low-maintenance as possible and can be easily unpicked should anyone need to take over from me in the future!

 

 

Hi Andrew

 

                How much of your non-standardness has affected the database, do you think?

 

 

 

Hello all!

 

So, my quest to get the Lincoln repository onto a more standard EPrints install continues! Thanks for help with Ubuntu versions etc; I’ve now got that knowledge together and can start to look at the migration. I know I’ve asked this in the past, but my scope has changed slightly. Now, instead of looking at recreating our live repository like for like, I’m just looking at migrating the output data into a fresh EPrints installation and working from there.

 

I know I realistically have two options – importing from an EPrints XML dump off the main site or through a database dump. I’m assuming that in both cases I’ll need to bring over essential field definition, phrase and workflow files to avoid causing issues, and I’m assuming that, ideally, the database route would be best to make sure that any “in review” or hidden items are also brought across. Main qustions:

 

·         Am I right in this assumption?

·         Can I JUST bring out a subset of tables for the deposit data or do I have to do a full database export? I’d ideally prefer to not do the latter as there are customisations to the user table in our live EPrints that I’m trying to avoid replicating in this new environment.

·         Are there any gotchas I should be aware of?

 

Thanks, as always, in advance!

Andrew

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.