Outgoing

From ICISWiki

Jump to: navigation, search

Back to TABLE CHANGES v5.6

Representing an outgoing batch of seed with new tables
Representing IRGCIS data on incoming batches in IRIS




IRGCIS field Place in IRIS
ListNMS record for the outgoing batch
This will provide summary data for the incoming batch and the ListID on which to hang the donor and list of GIDs received






COUNTRY listnms.locid.institid.cntryid
ListID AutoID
IRGCREQNO ListName
LocID Points to the LocID of the requesting institute
RequestorID TeamMember.personid where teammember.role=requestor
ListType IntReq for internal requests; ExtReq for external requests. FLDNO in UDFLDS
RecipientID TeamMember.personid where teammember.role=recipient
ListName Batch ID as assigned in GRIMS
SupervisorID TeamMember.personid where teammember.role=supervisor
ListDesc Description of the shipment
AddressID TeamMember.addressID where role=requestor
ListDate Date list processed
DATEREQ ListNMS.EventStart
EventStart Date of receipt of request; YYYYMMDD
DATE_REL ListNMS.EventEnd
EventEnd Date seeds released from GRC: YYYYMMDD
DEPT From Address where role=requestor
EventSponsor

OFFICE_INST From Address where role=requestor
ListUID UserID
ADDRESS_ST From Address where role=requestor
EventRef  ? Is Bibrefs to be used for pointers to scanned documents
ADDRESS_CITY From Address where role=requestor
EventDocs URL of location where scanned documents are held
POST_CODE
LHIERARCHY (Need LISTNMS record of type FOLDER for GRC incoming batches)
ORGTYPE listnms.locid.institid.instype
LISTSTATUS

REQUEST_TYPE ListNMS.ListType





TeamMember record for the outgoing batch



MemberID AutoID
Not to be retained - not used or embodied within the above
ListID = ListID for the batch
REQUESTOR
MemberNo Up to 6, for the 6 roles (requestor, recipient, supervisor, authorizer, consignee, port of entry). Obligatory entries for requestor and recipient (duplicate personid and addressid if it’s the same person
DATE_SHIP
PersonID The ID of the Team member. Links to PersonID in Persons
NAME_IRS
AddressID The ID of the address associated with the different roles
SUPVSR_LNAME
MemberRole Requestor, recipient, supervisor, authorizer, consignee, port of entry: FldNo in UDFLDS
SUPVSR_FNAME
CNTRYID Country in which collecting mission was undertaken
SD_RECIPIENT
LRPLCE

REQUESTOR_LNAME



REQUESTOR_FNAME
ListNMS record for the mission
This will hold the summary details of the mission, and provide the ListID on which to hang the collecting team and the list of GIDs collected






REQUESTOR_IONAME
ListID AutoID
SD_RECIPIENT_LNAME
LocID Points to the location/region within which the collecting mission took place (above)
SD_RECIPIENT_FNAME
ListType COLLMISS. FLDNO in UDFLDS
SD_RECIPIENT_IONAME
ListName Name of the collecting mission
CCODE
ListDesc Description of the collecting mission


EventStart Start date of the collecting mission; YYYYMMDD
To be retained in a separate reduced "Seed_Requestor" table kept only in IRIS-GRC-local - as these are data used only internally for processing the batch
EventEnd End date of the collecting mission: YYYYMMDD
PURPOSE
EventSponsor Name of the body sponsoring or funding the collecting mission
DISPATCH_MODE
EventUID UserID
TOT_SUPP
EventRef Report or related reference to the collecting mission. Links to RefID in BIBREFS
TRAIT_EVAL
EventDocs URL of location where scanned documents are held
REQ_STAT
LHIERARCHY (Need LISTNMS record of type FOLDER for Collecting Missions)
PRN_LABEL
LISTSTATUS

SHU_CERTIF



PICK
TeamMember records for the mission: one for each member of the collecting team
This will specify all members of the collecting team






DISTINCT_ACCNO
MemberID AutoID
OLD_REQNO
ListID = ListID for the collecting mission
GERMPLASM_TYPE
MemberNo Sequential number (arbitrary?) for each person within the team
COMMENT_REQSTAT
PersonID The ID of the Team member. Links to PersonID in Persons
SPP_CODE
AddressID The ID of the address of the team member for the purposes of this event
ASSIGN_PLOT
MemberRole Normally just Collector? (FldNo in UDFLDS)
GB_REQUEST

Personal tools