Hi Dan,
I suspect it may be related to this:
https://github.com/eprints/eprints3.4/blob/d805362779e1bab2451531061e932c034702b63f/perl_lib/EPrints/DataObj/EPrint.pm#L247

 

The corresponding block in v3.3 is:
https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/DataObj/EPrint.pm#L198-L247

- which doesn't have the 'export_as_xml=>0,' flag.

 

One approach to solve this (entirely untested!) would be to replace the core field in an archive specific config file e.g.:
~/archives/ARCHIVE/cfg/cfg.d/zz_export_item_issues.pl

push @{ $c->{fields}->{eprint} },  {

### a copy of the definition of the field in the first link above, and:

  export_as_xml => 1,

  replace_core=>1

};

 

> I’m a sysadm, not a dev.

 

I've put the following gist together which might be easier - incase the perl gets mangled in email form:

https://gist.github.com/jesusbagpuss/b1720d3ea23ac1ff7201a3263a247713

 

Put that file in e.g. ~/archives/ARCHIVE/cfg/cfg.d/zz_export_item_issues.pl

run bin/epadmin test ARCHIVEID

try an export of one eprint - see if it's helped!

 

Cheers,

John

 

 

 

 

Old server: Ubuntu 16.04LTS with EP 3.3.15. Worked great for years.

migrating to

New server: Ubuntu 18.04LTS, apt installed EP 3.4.1 from http://deb.eprints-hosting.org/3.4/stable/; manually downloaded & unzipped publication flavor v3.4.1.

 

After setup of the new server, to verify that all data came over, I compared a complete XML export from the 3.3.15 server to a complete XML export from the 3.4.1 server, both using the ~/bin/export CLI tool.

 

The 3.3.15 export correctly contains <item_issues> tags & corresponding subtags. The 3.4.1 server correctly imports the <item_issues>, as they are visible on the 3.4.1 web pages, but it does not export any <item_issues> tags / subtags at all.

 

I’d like the 3.4.1 export to contain the <item_issues> tags, as next time I do a migration like this I’ll want that data to be moved over to the newer machine.

 

I’m a sysadm, not a dev. I have basic perl skills, but looking at ~/perl_lib/EPrints/Plugin/Export/XML.pm, I don’t understand how XML export works or where the actual heavy lifting occurs.

 

Suggestions?

 

Thanks,

Dan Stieneke

IT Specialist

AFM ITSD

USDA - ARS - NWISRL

3793 N 3600 E

Kimberly, ID 83341

 

This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.