Versions Compared

Old Version 1

changes.mady.by.user Jordan Lamb

Saved on

compared with

New Version Current

changes.mady.by.user Jordan Lamb

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status

Jira Legacy
serverSystem JIRA
columnskey,updated,assignee,priority,status,resolution
maximumIssues20
jqlQuerykey = AP-140
serverId8b861ae3-ff87-316b-a17e-97c61a7e2fb4

Due date

Annual

On this page

Table of Contents
maxLevel2
minLevel2

❓ Problem statement

...

EB14 isn’t generating values since going baseline.SB38 is still null on submissions after it’s voluntary addition in 2019.

🔎 Research/Backup

Issue

EB14’s logic is unfortunately a lot simpler than we thought. That case is being partially tracked on this Ellucian case.

Background

Since going baseline we have only reported 5 distinct values for that field.

Proposal

We will have to use the DED values on validation table, GORRACE.

Actions

Jira Legacy
serverSystem JIRA
columnskey,summary,updated,due,assignee,priority,status,resolution
maximumIssues20
jqlQuerykey in (AP-143,AP-142)
serverId8b861ae3-ff87-316b-a17e-97c61a7e2fb4

Dependency StatementInvestigation

  • We do not intend to change the data on SPBPERS_ETHN_CODE (SPAIDEN Table, STVETHN Validation Table). According to https://sequoias.atlassian.net/l/c/y0YPx0nJit pulls from that field to populate Ethnicity_Code and ETHNICITY_DESC.

💎 Helpful SQL Queries

GORRACE Codes Used and their Description

...