EPrints Technical Mailing List Archive
Message: #01141
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Using a user metafield to control eprint workflow
- To: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Using a user metafield to control eprint workflow
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Tue, 2 Oct 2012 16:02:07 +0100
In our archive, we have a namedset for 'collections': collection1 collection2 collection3 ... This is used in an eprint to show which primary collection an item belongs to. I also want to use the same namedset in the user configuration to control which collections someone can deposit into: E.g. User has 'collection1' and 'collection3' selected in their profile, the first stage of the eprint workflow would be: Which collection? [] Collection 1 [] Collection 3 If a user only has access to one collection, this stage is skipped (as the field is set in the eprint_defaults.pl file). What is the best way to control the options available in the workflow based on the depositing user? It's similar to the 'user_review_scope.pl' - but at the depositing end of the process... I'm probably overlooking something very simple! Cheers, john
- Prev by Date: [EP-tech] Captcha / reCAPTCHA
- Next by Date: [EP-tech] Re: Using a user metafield to control eprint workflow
- Previous by thread: [EP-tech] Captcha / reCAPTCHA
- Next by thread: [EP-tech] Re: Using a user metafield to control eprint workflow
- Index(es):