Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DATA Act Schema Model 0.2 #89

Open
JenniferC opened this issue Jun 8, 2015 · 1 comment
Open

DATA Act Schema Model 0.2 #89

JenniferC opened this issue Jun 8, 2015 · 1 comment

Comments

@JenniferC
Copy link

1.What are all the USSGL account numbers required to be included in the DATA Act reporting. A comprehensive list for each of the derived DATA Act elements is required in order for the agency to correctly extract all the data.
2.Why does the list of data elements not include the TAS SubAccountSymbol while the schema document (on page 5) does?
3.Please correct the links inside the schema document to link to the related entry. Almost all of the links are linking back to section 4.1. For example the link for USSGLentryHeader (on page 6) under 6.1 should link to section 6.1.1 but links to section 4.1 Agency.
4.The element appropriationAccount in Section 6.1.1 appears to be a duplicate of the TAS elements in section 4.2. Is this a concatenation of the TAS elements or something different?
5.The TAS element availabilityTypeCode (Proposed/Future) does not include clearing or cancelled accounts (F or C codes respectively). Is this intentional? This code is blank for annual or multi-year accounts in Component TAS for GTAS reporting. Please confirm this is intended for DATA Act reporting.
6.In section 6.1.1.2 is the accountDescription element the description of the USSGL account refered to in the element accountNumber? Would this be the name of the USSGL account from the USSGL listing? Each agency may have their own shorthand name for the USSGL account. Should the accountDescription be a look up element from the USSGL listing authoritative source (from Treasury)?
7.In Section 6.1 the period element is described as a two-digit number that has a leading zero for the period. The length characteristic states 1 and the example shown is a 6. This is inconsistent with the description. Which is correct?

@JenniferC
Copy link
Author

Additional Questions:

  1. The element agencyidentifier has a length of three but the example only shows two digits. Please make it consistent.
  2. The element programActivity is described as: "A specific activity or project as listed in the program and financing shedules of the annual budget of the United States Government." What level of activity is this expected to be? Is this the top level as listed on the SF-132 Apportionment or if an agency tracks that program at a more detailed level, at the detail level? Is this a code or text description? Is this for category A funds as well as category B funds?
  3. In the example for the element awardNumber, the Award ID is shown without the Address Activity Code as the first 6 numbers and incorrectly includes dashes in the number. The new AAC format should be shown in the example.
  4. The last sentence of the first paragraph in Section 5 (Derived DATA Act Elements) indicates that the data elements are considered summary level with a description of how those values are derived from the detailed account transaction-level data. Section 6.1.1 lists the data elements in section 5 with tags. Are the elements in section 6.1.1 the detailed transaction-level data? If so, does the agency have to provide the summary data elements in section 5?
  5. Please include page numbers for the document.

@JenniferC JenniferC reopened this Jun 9, 2015
mmeintelwade pushed a commit that referenced this issue Feb 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant