Open Government Transparency Search for phyllis anderson in us

Search inside dataset "ALLPENSIONS" (e.g., "john smith")

(optional sorting)

Preview of information for phyllis anderson in us

PHYLLIS ANDERSON retired on 1998-04-30T00:00:00.000 from FERNALD DEVELOPMENTAL CENTER, where she had worked for 160225.00 days. Her last agency was 2220, and her retirement type is SA. At the time of her retirement, she was 69 years old and her average salary was 20565.66. Her annual pension is 13057.20 and her monthly pension is 1088.10. Her person ID is 173435 and her transaction number is 36941868. This information is current as of 2016.

Profile (requires free login with Google Account) Profile
Save to Profile

Open Data Search (show all US catalogs)
Open Data Search (show all EU catalogs)


Total datasets: 1 load time 0.08 min

ALLPENSIONS null 2016-11-30T18:14:04.000Z Search

{"serviceMillis":1013,"searchMillis":[393,236]}

type_of_retirementannual_pensionagency_last_worked_increditable_serviceaverage_salarydate_of_retirementfirst_namelast_nameyeartrans_noage_at_retirementdepartment_last_worked_inmonthly_pensionperson_id
SA13057.202220160225.0020565.661998-04-30T00:00:00.000PHYLLISANDERSON20163694186869FERNALD DEVELOPMENTAL CENTER1088.10173435


  data:
    [
   {
      "type_of_retirement": "SA",
      "annual_pension": "13057.20",
      "agency_last_worked_in": "2220",
      "creditable_service": "160225.00",
      "average_salary": "20565.66",
      "date_of_retirement": "1998-04-30T00:00:00.000",
      "first_name": "PHYLLIS",
      "last_name": "ANDERSON",
      "year": "2016",
      "trans_no": "36941868",
      "age_at_retirement": "69",
      "department_last_worked_in": "FERNALD DEVELOPMENTAL CENTER",
      "monthly_pension": "1088.10",
      "person_id": "173435"
   }
]

  keys:
    [
   "type_of_retirement",
   "annual_pension",
   "agency_last_worked_in",
   "creditable_service",
   "average_salary",
   "date_of_retirement",
   "first_name",
   "last_name",
   "year",
   "trans_no",
   "age_at_retirement",
   "department_last_worked_in",
   "monthly_pension",
   "person_id"
]
    

directoryQuery: https://api.us.socrata.com/api/catalog/v1?ids=3zah-qrsj&limit=100

permalink: https://cthru.data.socrata.com/d/3zah-qrsj

dataQuery: https://cthru.data.socrata.com/resource/3zah-qrsj.json?$select=type_of_retirement%2Cannual_pension%2Cagency_last_worked_in%2Ccreditable_service%2Caverage_salary%2Ctitle_at_retirement%2Cdate_of_retirement%2Cfirst_name%2Clast_name%2Cyear%2Ctrans_no%2Cage_at_retirement%2Cdepartment_last_worked_in%2Cmonthly_pension%2Cperson_id%2Cmiddle_initial&$order=first_name%20desc&$limit=10&$offset=0&$q=phyllis%20anderson

Sites such as socrata.com appear to be tools to bring transparency to our governments. But what do they actually do in practice. This site attempts to use socrata.com (and hopefully all other "open transparency sites") to understand what the state of affairs are at the moment.

A summary view of the catalog when you filter for the word salary shows the lack of standarization.

Employee Salaries This dataset provides base salary information abou... Ramona Benson, Department of Human Resources Search
Current Employee Names, Salaries, and Position Tit... This dataset is a listing of all active City of Ch... City of Chicago Search
Budget - Salaries Budgeted Salaries by Position null Search
State of Vermont Employee Salaries Salary information for State of Vermont active emp... Department of Human Resources Search
Title and Salary Listing The Title and Salary Listing is a compilation of j... New York State Department of Civil Service Search
    

The screenshot shows a sample of name and descriptions of government uploaded salary transparency information. First of all, the information appears to be not easy to find for the general public. And even if the general public finds it, it is hard to tell what government it applies to. For example, there are datasets that simply have the name "Employee Salaries" and some that have no attribution at all. The column names are a mix of whatever the hundreds of individuals decided to use. This makes organization difficult, but not impossible.

Let's organize the information and overcome the obstacles!

Socrata Meta Catalog API

The Socrata Meta Catalog API provides access to metadata about the datasets and tables available on the Socrata Open Data Portal.

Getting Started

  1. Create a Socrata developer account at https://dev.socrata.com.
  2. Get an API access token from the API Access Tokens page.
  3. Send a GET request to the /catalog/v1 endpoint with the following parameters:

For example, the following request will return a list of all the datasets available on the City of Boston's Open Data Portal:

GET https://data.boston.gov/catalog/v1?access_token=YOUR_ACCESS_TOKEN

The response will be a JSON object containing an array of dataset objects. Each dataset object will contain the following properties:

Using the API

The Socrata Meta Catalog API can be used to perform a variety of tasks, such as: For more information on how to use the API, please refer to the Socrata Meta Catalog API documentation.

Not seeing what you are looking for:
Ask your question here (include email if you want an answer)

To stay updated subscribe here:
    debug: columns: name:
    [
   "AGE AT RETIREMENT",
   "AGENCY LAST WORKED IN",
   "ANNUAL PENSION",
   "AVERAGE SALARY",
   "CREDITABLE SERVICE",
   "DATE OF RETIREMENT",
   "DEPARTMENT LAST WORKED IN",
   "FIRST NAME",
   "LAST NAME",
   "MIDDLE INITIAL",
   "MONTHLY PENSION",
   "PERSON ID",
   "TITLE AT RETIREMENT",
   "TRANS NO",
   "TYPE OF RETIREMENT",
   "YEAR"
]

    debug: columns: type:
    [
   "Calendar date",
   "Number",
   "Number",
   "Number",
   "Number",
   "Number",
   "Number",
   "Number",
   "Number",
   "Text",
   "Text",
   "Text",
   "Text",
   "Text",
   "Text",
   "Text"
]