Difference between revisions of "App/otu/show material"
From mx Help Wiki
(→Updating/regenerating IPT/GBIF records) |
|||
(2 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | + | == Updating/regenerating IPT/GBIF records == | |
+ | * If the total number of specimen and lot records is less than a cutoff (currently 500 of each) a 'Rebuild records' link is available. If the number of records is greater than the cutoff ipt records must be generated at the project level. | ||
+ | * Clicking the "Rebuild records' link will attempt to generate corresponding records in the ipt_records table. A status message is returned. | ||
+ | * There are several possible reasons a record can fail to be built: | ||
+ | *# The associated OTU is not tied to a taxon name. | ||
+ | *# The specimen or lot is no tied to collecting event. | ||
+ | *# The specimen or lot does not have at least one identifier. | ||
+ | *# The project does not have a default institution/repository set | ||
+ | *# The project does not have a collection code set. |
Latest revision as of 12:31, 26 April 2011
[edit] Updating/regenerating IPT/GBIF records
- If the total number of specimen and lot records is less than a cutoff (currently 500 of each) a 'Rebuild records' link is available. If the number of records is greater than the cutoff ipt records must be generated at the project level.
- Clicking the "Rebuild records' link will attempt to generate corresponding records in the ipt_records table. A status message is returned.
- There are several possible reasons a record can fail to be built:
- The associated OTU is not tied to a taxon name.
- The specimen or lot is no tied to collecting event.
- The specimen or lot does not have at least one identifier.
- The project does not have a default institution/repository set
- The project does not have a collection code set.