EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #06094
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Custom validation and new MetaFields (institutional id, orcid id)
- To: Eprints Tech Mailing List <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Custom validation and new MetaFields (institutional id, orcid id)
- From: "Graham, Clinton T" <ctgraham@pitt.edu>
- Date: Fri, 18 Nov 2016 14:36:19 +0000
We are soliciting an Institutional ID and ORCID ID for our users and for our deposits.
Each of these require custom validation.
It seems the best place for this validation is in field_validate.pl, presumably by creating new
MetaFields for each of these entries and keying on the new
MetaField types. Is this standard practice?
A brief search doesn't pull documentation or examples of
subclassing new MetaFields. Are there any concerns with adjusting the field types for these fields, for which data already exists in deposited records? Enjoy, - Clinton Graham Systems Developer University of Pittsburgh | University Library System 412-383-1057 |
- Prev by Date: Re: [EP-tech] Debug Creator browse view generation
- Next by Date: Re: [EP-tech] Custom validation and new MetaFields (institutional id, orcid id)
- Previous by thread: [EP-tech] Open Repositories Conference Update: OR2017 Proposal Deadline Extended
- Next by thread: Re: [EP-tech] Custom validation and new MetaFields (institutional id, orcid id)
- Index(es):