The intial part of this is really cleaning up the workflow so that we only have one field to work with. As the most used field is the Print ISSN I’m thinking of converting that to having the sub-type however it then comes down to how I handle the data in the online field - Bev says she’s happy manually moving the data over however if I can do it programmatically for her then that would probably be better.

 

 

I was going to suggest something similar - like the way the datesdatesdates plugin works.

See: https://github.com/eprintsug/datesdatesdates/blob/master/lib/cfg.d/zz_datesdatesdates_triggers.pl#L3-L45

It chooses the *best* (most published) date to promote to the default field - which works well with export plugins that reference the default 'date' field.

 

Do your academics know whether an ISSN is print or online? Do you trust them to assert this accurately?

 

I'd possibly apply the logic:

If there's only one ISSN in your repeatable field, promote that to the default ISSN field.

If there are two (or more), prefer one.

 

*But* really you should be thinking about exposing all this data to other downstream systems (which would mean altering export plugins to output multiple ISSNs…)

 

Cheers,

John

 

 

You could have a Print ISSN field and an Online ISSN field, and then an ISSN field which is virtual (or automatic) and selects an appropriate ISSN from the two and returns it.  That way the user would have two explicitly labelled fields, but the behavior of the issn field could be programmatically controlled.

 

--

Adam

 

Hello!

 

So, I’m trying to sort out an issue in our EPrints where we have two ISSN fields – a Print ISSN and an Online ISSN. The problem with these is that neither of these fields are the ACTUAL ISSN which causes some issues on both output as well as making adding records clunky to ensure that academics put their ISSN in the correct field.

 

What I’m looking at doing is adding a “Type” dropdown to the Print ISSN definition that can toggle the ISSN to Print or Online, change the phrase on the Print ISSN field to just identify it as an ISSN (it’s already repeatable) and make sure that the ISSN field is included in the export. There are a few potential “gotcha’s” with this that I’m concerned about.

 

·         Will doing this jeapordise the existing data in any way?

·         If I set the default to “Print” will this default any pre-existing records to a Print type?

·         At the moment we’re looking at manually moving the Online ISSN’s over to the new field, however if there is an easy way to consolidate these two fields I’m all ears! J

 

Thanks in advance!

 

Andrew

*** 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/ *** EPrints developers Forum: http://forum.eprints.org/