Remember
that since Abstracts is mainly a Web-based system, for each of the codes
and subcodes you create, you will need to check the “Available to Web”
checkbox.
The following table describes the system types for the ABS subsystem. Prior to working with the ABS system, you must create codes (and in some cases, subcodes) for each of the non-fixed system types.
Remember
that since Abstracts is mainly a Web-based system, for each of the codes
and subcodes you create, you will need to check the “Available to Web”
checkbox.
Type |
Fixed Codes? |
Description |
|---|---|---|
| ANSWER_TYPE | Y | This identifies the type of answer that can be provided as
answers to the submitter (author) disclosure question, submission
disclosure questions, and content (text block) questions.
The following values are delivered with base and cannot be modified or added to:
Reviewer scoring questions only use the following answer types:
This code is selected for the ANSWER_TYPE_CODE fields in the following tables:
|
| ASSIGNMENT_STATUS | Y | This identifies the status of the reviewer's assignment to
review a submission. When a reviewer is assigned to a submission,
the initial ASSIGNMENT_STATUS is “INVITED”. The reviewer has the
option to decline the invitation, in which case the status is
updated to "DECLINED". When the reviewer accepts the
invitation, the status is updated to “UNDER_REVIEW”. When the
reviewer answers the scoring questions, the status is updated
to "COMPLETED”.
Reviewer submission scores can only be entered by reviewers with a status of “UNDER_REVIEW”. The following values are delivered with base and cannot be modified or added to:
This code is selected for the ASSIGNMENT_STATUS_CODE field in the ABS_SUBMISSION_REVIEWER table. |
| ASSIGNMENT_STATUS_REASON | N/A | This system code has not been implemented. |
| AUTHOR_DISCLOSURE_ANSWER | N | This identifies the answer code associated with the subcode
values that can be selected as the answer to the submitter disclosure
question.
If, during submission type setup, the answer type is defined as "DROP_DOWN" or "YES_NO", then the submitter disclosure answer code must be defined by selecting a code value for this code. The following values are delivered with base:
For example, if the author disclosure question is "Select your highest level of education." you might define an author disclosure answer code as "HIGHEST_EDUCATION_LEVEL" with subcode values of "HIGH_SCHOOL", "BACHELORS", "MASTERS", and "DOCTORATE". This code is selected for the AUTHOR_DISCLOSURE_ANSWER_CODE field and the DEFAULT_AUTHOR_DISCLOSURE_ANSWER_CODE field in the ABS_CALL_SUBMISSION_TYPE_AUTHOR_DISCLOSURE_CONTROL table. Subcode values for this code are selected for the AUTHOR_DISCLOSURE_ANSWER_SUBCODE field in the ABS_SUBMISSION_AUTHOR_DISCLOSURE table. |
| AUTHOR_ROLE | N | This code is not visible to the end user. This code is set
based on the submitter's response to the question "Are you
an [author] on this submission?" when first submitting a
submission. (The word author in brackets is dependent on the setup
by the administrator.)
If the submitter answers that they are an [author] on the submission, the system sets this code to AUTHOR. If the submitter answer that they are NOT an [author] on the submission, then the system sets this code to NON_AUTHOR-SUBMITTER. This code is selected for the AUTHOR_ROLE_CODE field in the ABS_SUBMISSION_AUTHOR table. |
| BLOCK_TYPE | N/A | Currently, this code is not being used in the system. |
| CALL_TYPE | N | This code identifies the type of call for participation. For
example, “MEETING”, “PUBLICATION”, etc. This field is used as
a search parameter when searching for a call.
This code is selected for the CALL_TYPE_CODE in the ABS_CALL table. |
| CATEGORY | N | This optional code allows your organization to categorize submissions
according to your needs. This could be coordinated with a meeting’s
session tracks or topic areas.
Another use of this code is to function as an alternative submission type code. Some organizations accept all submissions under a single type. After the organization reviews the submission, they make a decision as to the best submission type for the submission. However, you cannot change submission types in Personify. Therefore, this code can be used for this purpose. An administrator can decide whether they want to use this code in the call submission type and whether submitters can enter a value for this code. If the organization is going to use this code as an alternate submission type, as stated above, they would not want the submitter setting this code. They would want an administrator to set it. This code is selected for the CATEGORY_CODE field in the ABS_SUBMISSION table. |
| CONTRIBUTOR_DESIGNATION | N | This identifies how contributors (submitters) will be labeled
during the submission process. For example, if your organization
wants to use the ABS system for accepting volunteer application,
the contributor would be an APPLICANT, not an AUTHOR.
The following values are delivered with base:
This code is selected for the CONTRIBUTOR_DESIGNATION_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| DISCLOSURE_ANSWER | N | This identifies the answer code associated with the subcode
values that can be selected as the answer to the submission disclosure
question.
If, during submission type setup, the answer type is defined as "DROP_DOWN" or "YES_NO", then the disclosure answer code must be defined by selecting a code value for this code. The following values are delivered with base:
This code is selected for the DISCLOSURE_ANSWER_CODE field and the DEFAULT_SUBMISSION_DISCLOSURE_ANSWER_CODE field in the ABS_CALL_SUBMISSION_TYPE_DISCLOSURE_QUESTION_CONTROL table. Subcode values for this code are selected for the DISCLOSURE_ANSWER_SUBCODE field in the ABS_SUBMISSION_DISCLOSURE table and the REJECTION_DISCLOSURE_ANSWER_SUBCODE field in the ABS_CALL_SUBMISSION_TYPE_DISCLOSURE_QUESTION_CONTROL table. |
| DISCLOSURE_QUESTION | N | This required code is associated with each submission disclosure
question definition. It can be used for reporting. For example,
if questions are related to the funding of the research of the
submission, a disclosure question code of "FUNDED_BY"
can be used.
The following values are delivered with base:
|
| DISCLOSURE_RELATIONSHIP | N | This required code is associated with each author disclosure
question. It can be used for reporting. For example, if questions
are of a financial nature, a disclosure relationship code of "FINANCIAL"
can be used.
The following values are delivered with base:
|
| EMAIL_TO | N/A | This code has not been implemented. |
| EXPERTISE | N | This identifies the areas of experience for reviewers. Reviewers
are matched to submissions by comparing the submission topic codes
to the reviewer’s areas of expertise. For example, Dentistry,
Pediatrics, Orthopedics, etc.
Expertise subcodes can also be defined for expertise codes. The following values are delivered with base:
This code is selected for the EXPERTISE_CODE field in the ABS_REVIEWER_EXPERTISE table. Subcode values are selected for the EXPERTISE_SUBCODE field in ABS_REVIEWER_EXPERTISE table. |
| EXPERTISE_LEVEL | N | This identifies the expertise level of a reviewer's area of
expertise. It is also used in defining the audience level of expertise.
The "EXPERTISE_LEVEL" code should be defined with a numeric value that identifies the highest level of expertise to the lowest level of expertise. This is defined in the Option 1 field. For example, Industry Expert may be given a numeric value of 3, Knowledgeable may be given a numeric value of 2, and Some Knowledge may be given a numeric value of 1. The ABS500 batch process matches reviewers to submissions by selecting reviewers with the highest level of expertise in the areas of expertise that match the submission topics. It is important that the highest level of expertise be given the highest numeric value. The following values are delivered with base:
This code is selected for the EXPERTISE_LEVEL_CODE fields in the following tables:
|
| EXTERNAL_STATUS | Y | This identifies the status of the submission in the review
process. The external status is the status that is viewed by submitters.
Administrator decisions, reviewer actions, and setups defined in Abstract Call Submission Type cause the external status to be set on submissions. Organizations select their unique review process setups during submission type setup. The following values are delivered with base and cannot be modified or added to:
This code is set for the EXTERNAL_STATUS_CODE field in the ABS_SUBMISSION table. |
| EXTERNAL_STATUS_REASON | N/A | This code has not been implemented. |
| FILE_TYPE | N | If your organization allows submitters to upload files as part
of their submission, this identifies the file extension of files
that can be uploaded.
The following values are delivered with base:
This code is selected for the FILE_TYPE_CODE fields in the following tables:
|
| FINALIST_STAGE | Y | This code is not visible to the end user. It is contained in
the ABS_REVIEW_PROCESS_BASE table. This table contains review
process event records that are copied to call submission types
based on setups defined for the call submission type. It is these
review process event records that automate the setting of the
external and internal status codes on submissions.
This code identifies whether the review process event is connected with a finalist stage. The finalist stage is an optional step in the review process before final accept/reject decisions are made about the abstracts. When review process records are created for a submission type within a call, if the organization has a finalist stage as part of the steps in their review process, all review-process events associated to the finalist stage are copied to the submission type review process table. The following values are delivered with base:
This code is set for the FINALIST_STAGE_CODE field in the ABS_REVIEW_PROCESS_BASE table. |
| INSTRUCTION_TYPE | N | In the base Abstracts Web application, user-defined instructions
can be displayed on various pages, based on the instruction type.
For example, if instructions are created for the "SUBMISSION_THANK_YOU"
instruction type, that displays on the confirmation page after
the author submits his/her paper.
The following values are delivered with base:
|
| INTERNAL_STATUS | Y | This identifies the status of the submission in the review
process. The internal status is the status that is viewed by administrators
and staff.
Administrator decisions, reviewer actions, and setups defined in Abstract Call Submission Type cause the internal status to be set on submissions. Organizations select their unique review process setups during submission type setup. The following values are delivered with base and cannot be modified or added to:
This code is set for the INTERNAL_STATUS_CODE field in the ABS_SUBMISSION table. |
| INTERNAL_STATUS_REASON | N/A | This code has not been implemented. |
| LEAD_RVWR_RECOMMENDATION | N/A | This code has not been implemented. |
| PARTICIPATION_REASON | N/A | This code has not been implemented. |
| PARTICIPATION_STATUS | Y | This code identifies whether a reviewer is currently active.
This code is not visible to the end user and is set to "ACTIVE".
This code is set for the PARTICIPATION_STATUS_CODE field in the ABS_CALL_SUBMISSION_TYPE_REVIEWER table. |
| PRELIMINARY_DECISION | N/A | This code has not been implemented. |
| PRODUCT_TYPE | Y | If your call is going to be linked to a meeting, the "M"
and "S" meeting product type codes must have the Web Enabled checkbox selected.
This code is defined for the MTG subsystem.
If your call is going to be linked to a subscription product, the "I" subscription product type code must have the Web Enabled checkbox selected. This code is defined for the SUB subsystem. |
| REJECTION_ANSWER | N | Submission disclosure questions can be defined so that a particular
answer will result in the submission not being acceptable to the
organization. If a submission is submitted with a reject answer
to a submission disclosure question, the submission status will
be set to "DECLINED". In this way, the administrator
can review the submissions on a case-by-case basis and contact
submitters for more information.
For example, an answer of “YES” to any of the following questions might mean that the abstract cannot be accepted: “Does your paper contain classified material?” or “Has your paper been presented at any other conferences?” The rejection answer is selected from the codes defined for the DISCLOSURE_ANSWER. The following values are delivered with base:
This code is selected for the REJECTION_ANSWER_SUBCODE field in the ABS_CALL_SUBMISSION_TYPE_DISCLOSURE_QUESTION_CONTROL table. |
| REQ_MULTIPLE_REVIEWERS | Y | This code is not visible to the end user. It is contained in
the ABS_REVIEW_PROCESS_BASE table. This table contains review
process event records that are copied to call submission types
based on setups defined for the call submission type. It is these
review process event records that automate the setting of the
external and internal status codes on submissions.
This identifies whether the organization's review process involves multiple reviewers reviewing a submission. If multiple reviewers are required, additional logic is needed to determine when all of the steps required for a reviewer-related event are completed for a submission. When review process records are created for a submission type within a call, if the organization requires multiple reviewers for each submission as part of the steps in their review process, all review-process events associated with multiple reviewers are copied to the submission type review process table. The following values are delivered with base and cannot be modified or added to:
|
| REQ_SEPARATE_LEAD_REVIEW | N/A |
This code has not been implemented. |
| REVIEW_BLIND_RULE | Y | This identifies whether the review process is Double-blind,
Single-blind, or Open for this submission type. The system checks
the code selected here and displays information to the reviewer
and/or author based upon the selection.
Currently, this code is not visible to the end user. The system sets this code to Double Blind. The following values are delivered with base and cannot be modified or added to:
This code is set for the REVIEW_BLIND_RULE_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| REVIEW_PROCESS_EVENT | Y | This code visible in the submission history. The review process
event is an event that happens in the submission review or selection
process that causes either the internal or external status of
the submission to change.
Any change to the internal or external submission status and the reviewer assignment status causes the system to create a record in the Abs_Submission_Activity table, which includes the event code. This code is set for the REVIEW_PROCESS_EVENT_CODE field in the ABS_SUBMISSION_ACTIVITY table. |
| REVIEW_TYPE | Y | This identifies whether the review process is using reviewers
or review boards. This code is not visible to the end user. The
system sets this code to "REVIEWER".
The following values are delivered with base and cannot be modified or added to:
This code is set for the REVIEW_TYPE_CODE field in the ABS_CALL_SUBMISSION_TYPE and ABS_REVIEW_PROCESS_BASE tables. |
| REVIEWER_APPOINTMENT | N | This code is not visible to the end user. The system sets this
code to "APPOINTED". This code is used in the ABS_REVIEWER_TERM
table.
The following values are delivered with base:
|
| REVIEWER_APPROVED_FOR | N | This identifies the type of material that the reviewer is approved
to review. Also, when a call submission type is defined, the type
of material that a reviewer must be approved to review will also
be defined using this code. Only reviewers with a current, active
term, who have the same REVIEWER_APPROVED_FOR code as defined
for the call submission type can be assigned to the call submission
type and submissions within that submission type.
If an organization wants a reviewer to be able to review any type of material, a REVIEWER_APPROVED_FOR code can be set to "ALL". If an organization wants to be able to assign any current reviewer to a call submission type, the REVIEWER_APPROVED_FOR code for the call submission type can also be set to "ALL". If the REVIEWER_APPROVED_FOR code for a call submission type is NOT set to "ALL", reviewers with an REVIEWER_APPROVED_FOR code of "ALL" can still be assigned to that call submission type. The following values are delivered with base:
|
| REVIEWER_EVAL_CRITERION | N/A | This code has not been implemented. |
| REVIEWER_EVAL_SCORE | N/A | This code has not been implemented. |
| REVIEWER_ROLE | N/A | This code has not been implemented. |
| REVIEWER_SOURCE | N/A | This code has not been implemented. |
| REVIEWER_STATUS | N/A | This code has not been implemented. |
| SCORING_ANSWER | N | This identifies the answer code associated with the subcode
values that can be selected as the answer to the reviewer scoring
question.
If, during submission type setup, the answer type is defined as "DROP_DOWN", then the scoring answer code must be defined by selecting a code value for this code. The following values are delivered with base:
This code is selected for the SCORING_ANSWER_CODE field in the ABS_CALL_SUBMISSION_TYPE_SCORING_CONTROL table. |
| SCORING_CRITERION | N | This identifies the criterion on which the submission is being
scored by the reviewer. This can be used for reporting.
The following values are delivered with base:
|
| STAFF_OR_REVIEWER | N/A | This code has not been implemented. |
| STAFF_REVIEW_STAGE | Y | This code is not visible to the end user. It is contained in
the ABS_REVIEW_PROCESS_BASE table. This table contains review
process event records that are copied to call submission types
based on setups defined for the call submission type. It is these
review process event records that automate the setting of the
external and internal status codes on submissions.
This code identifies whether the review process event is connected with an initial staff review stage. The staff review stage is an optional step in the review process before reviewers are assigned to any submissions. When review process records are created for a submission type within a call, if the organization has a staff review stage as part of the steps in their review process, all review-process events associated to the staff review stage are copied to the submission type review process table. The following values are delivered with base:
|
| STAFF_ROLE | N | This identifies the role of the staff selected. This can be
used for reporting, but otherwise has no other functionality in
the application.
This code is selected for the STAFF_ROLE_CODE field in the CUS_ABS_STAFF_ROLE table. In addition, the system sets the STAFF_ROLE_CODE field in the ABS_CALL_SUBMISSION_TYPE_STAFF table. |
| SUBMISSION_ACTIVITY_TYPE | N/A | This code has not been implemented. |
| SUBMISSION_KEYWORD | N | This identifies the submission keyword code associated with
the subcode values that can be selected as keywords of submissions
to the call submission type. This allows the organization to maintain
subsets of keyword codes so that different sets of keywords can
be used for multiple calls.
During submission creation the submitter will select the keywords from the subcodes defined for this code. Administrators can define whether keywords are to be used during the submission creation. This code is set for the VALIDATION_KEYWORD_CODE field in the ABS_CALL_SUBMISSION_TYPE table. Subcode values are selected for the KEYWORD_CODE field in the ABS_SUBMISSION_KEYWORD table. |
| SUBMISSION_TOPIC | N | This identifies the submission topic code associated with the
subcode values that can be selected as topics of submissions to
the call submission type. This allows the organization to maintain
subsets of topic codes so that different sets of topics can be
used for multiple calls.
During submission creation the submitter will select the topics from the subcodes defined for this code. Administrators can define whether topics are to be used during the submission creation. If a review process will be used for the call submission type, the ABS500 batch process can be defined to automatically assign reviewers to submissions by comparing submission topics with reviewers' areas of expertise. This code is set for the VALIDATION_TOPIC_CODE field in the ABS_CALL_SUBMISSION_TYPE table. Subcode values are selected for the TOPIC_CODE field in the ABS_SUBMISSION_TOPIC table and for the PRIMARY_TOPIC_CODE field in the ABS_SUBMISSION table. |
| SUBMISSION_TYPE | N | This identifies the submission type code of the submission
type you are you are creating. Codes delivered with the base application
include the following:
|
| TEXT_BLOCK_ANSWER | N | This identifies the answer code associated with the subcode
values that can be selected as the answer to the text block questions.
Text block questions are the general content questions that administrator
define for submitters to answer.
If, during submission type setup, the answer type is defined as "DROP_DOWN" or "YES_NO", then the text block answer code must be defined by selecting a code value for this code. During submission type creation the submitter will select the answer to the text block question from the subcodes defined for this code. The following values are delivered with base:
This code is set for the TEXT_BLOCK_ANSWER_CODE field and the DEFAULT_TEXT_BLOCK_ANSWER_CODE in the ABS_CALL_SUBMISSION_TYPE_TEXT_BLOCK_CONTROL table. Subcode values are selected for the TEXT_BLOCK_CONTROL field in the ABS_SUBMISSION_TEXT_BLOCK table and for the DEFAULT_TEXT_BLOCK_ANSWER_CODE in the ABS_CALL_SUBMISSION_TYPE_TEXT_BLOCK_CONTROL table. |
| VALIDATE_KEYWORD_CONTROL | Y | This code is not visible to the end user. The system sets this
code to "SYSTEM_LIST".
The following values are delivered with base:
This code is set for the VALIDATE_KEYWORD_CONTROL_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| VALIDATE_TOPIC_CONTROL | Y | This code is not visible to the end user. The system sets this
code to "SYSTEM_LIST".
The following values are delivered with base:
This code is set for the VALIDATE_TOPIC_CONTROL_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| VALIDATION_KEYWORD | N | If a submission type has been defined to validate submission
keywords using system types and codes (i.e., SYSTEM_LIST), this
code identifies the keyword code associated with the subcode values
that can be selected as the keywords on the submission. The keyword
codes are selected from subcodes where the ABS type is “SUBMISSION_KEYWORD”
and the code is the code selected here.
This field is only enabled if Validate Keywords Control Code = ‘SYSTEM_LIST’. This code is selected for the VALIDATION_KEYWORD_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| VALIDATION_TOPIC | N | If a submission type has been defined to validate submission
topics using system types and codes (i.e., SYSTEM_LIST), this
code identifies the topic code associated with the subcode values
that can be selected as the topics on the submission. The topic
codes are selected from subcodes where the ABS type is “SUBMISSION_TOPIC”
and the code is the code selected here.
This field is only enabled if Validate Topics Control Code = ‘SYSTEM_LIST’. This code is selected for the VALIDATION_TOPIC_CODE field in the ABS_CALL_SUBMISSION_TYPE table. |
| VISIBILITY | N/A |
This code has not been implemented. |
| WEB_SUBMITTAL_OVERRIDE | N/A | This code has not been implemented. |