1

Re: Not for dissemination

Trevor James has just posted a message onto our mailing list (archive of the message available here) which reminded me of a feature we've often needed. Essentially, we need to be able to mark records, preferably in batches (entire survey's for instance), as 'not for dissemination'. This flag would simply prevent records from being exported. It would be a bit like the confidential flag, but not as strong.

If you read Trevor's message, you'll see a condition of receiving harlequin ladybird data from the survey would be that the data should not be disseminated further. Now, unless we mark all of the records as confidential (which is akin to a sledgehammer and nut scenario) when and if we were to import them into our database, we have no easy way of stopping the records getting exported again. We have several other datasets that are strictly 'not for dissemination', but yet the records aren't confidential, and so we have to think very carefully about incorporating them into Recorder.

Do others have 'not for dissemination' datasets that would benefit from such a feature?

Charles

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

2

Re: Not for dissemination

Yes we do. This feature would be ace.

Lizzy Peat
HBIC

3

Re: Not for dissemination

I think so. I imagine data from third parties for example that should not be passed on. This is already a cause for concern with the threat of duplication. It's a concern with regard to the gateway. I know I will have fungi data sent to me soon that is already on the gateway for example.

Data Manger
Somerset Environmental Records Centre