Need to accommodate full text fields in CONTENTdm that do not have the nickname 'full'

[mjordan]

The "nicknames" that CONTENTdm assigns to fields internally is pretty consistent but in some cases it will assign unpredictable nicknames. Good example is that 'full' is the most common nickname for the field containing an object's full text, but we have encountered collections where the nickname is 'fullte'.

A simple hotfix is appropriate for now, but we probably should add a configuration option to the WRITER section of the .ini file to allow the user to specify the human-readable label of the full text field (which is available in the CONTENTdm field configuration settings), which we can then map to a nick for internal use.

[MarcusBarnes]

@mjordan Hotfix committed to master in 059b7def0dbb10ce5847ec7be5ff7387957000ec.

[mjordan]

Sweet, I'm in a meeting now but will test around 4 pm.

[MarcusBarnes]

@mjordan Thank you for testing. I've already tested the hotfix against a CT newspaper.

[mjordan]

Sorry, you can test now by running mik against the lat_m.ini file in mik_mark. Delete the lat_m output directory in production_loads first though. This config file is for generating 5 random samples. Use php -c php.ini so the FITS generation will not fail.

[MarcusBarnes]

@mjordan OK. I'll confirm the results once I've done so.

[MarcusBarnes]

@mjordan Tested lat_m locally with the hotfix in place. Worked as expected.

[mjordan]

Excellent, thanks. Let's leave this open so we can include it in the 1.0 milestone.