IFWIS Core v2.3

Overview | API | Model | About | Contact

Version Actions

GET https://fishandgame.idaho.gov/ifwis/core/version

Documentation of version actions (displays this page).

GET https://fishandgame.idaho.gov/ifwis/core/version/detail/{id}.{format}

Detail of version by VersionID (auto-incrementing primary key) Return format may also be provided. Html is default.

User must be a member of a group with read privileges, or the creator.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])

Examples

GET https://fishandgame.idaho.gov/ifwis/core/version/list/{id}.{format}

Lists versions tied to a NodeID. Return format may also be provided. Html form is default.

User must be a member of a group with update privileges, or the creator to view.

Parameters

  • id - NodeID
  • format - return format type (xml, inc, html[default])

Examples

GET https://fishandgame.idaho.gov/ifwis/core/version/fetchmy/{id}.{format}?orderBy={orderBy}&orderDir={orderDir}&page={page}&pageSize={pageSize}

Lists versions of a given Type (VocabID or Vocab) created by current user. Return format may also be provided. Html form is default.

User must be the creator.

Parameters

  • id - VocabID or Vocab
  • format - return format type (xml, inc, json, csv, html[default])
  • orderBy - NODE.AUD_NDate might be good
  • orderDir - 1 for DESC, 0 for ASC
  • page - Page Number
  • pageSize - Number of records on page

Examples

GET https://fishandgame.idaho.gov/ifwis/core/version/create/{id}.{format}

Create a new version by parent NodeID. Return format may also be provided. Html form is default.

User must be a member of a group with create.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])

Examples

POST https://fishandgame.idaho.gov/ifwis/core/version/create/{id}.{format}

Create a new version by parent NodeID. Return format may also be provided. Html is default.

User must be a member of a group with create privileges.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])
  • form variables
GET https://fishandgame.idaho.gov/ifwis/core/version/edit/{id}.{format}

Edit a version by VersionID (auto-incrementing primary key). Return format may also be provided. Html form is default.

User must be a member of a group with update privileges, or the creator edit.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])

Examples

POST https://fishandgame.idaho.gov/ifwis/core/version/edit/{id}.{format}

Commit edits to a version by VersionID (auto-incrementing primary key). Return format may also be provided. Html is default.

User must be a member of a group with update privileges, or the creator to edit.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])
  • form variables
POST https://fishandgame.idaho.gov/ifwis/core/version/delete/{id}.{format}

Deletes a version by VersionID. Return format to display detail may also be provided. Html is default.

User must be a member of a group with delete privileges.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])
POST https://fishandgame.idaho.gov/ifwis/core/version/initialize/{id}.{format}

Clone a version by VersionID (auto-incrementing primary key). Return format may also be provided. Html is default, returning the form in edit mode.

User must be a member of a group with create privileges.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])
POST https://fishandgame.idaho.gov/ifwis/core/version/release/{id}.{format}

Releases a node to be published and trigger review process for versions needing approval. Version is identified by VersionID (primary key). Return format to display detail may also be provided. Html is default.

User must be a member of a group with update privileges.

Parameters

  • id - VersionID
  • format - return format type (xml, inc, html[default])
  • yesno - 1 to publish, 0 to revoke publish

What is IFWIS Core?

  • An Overview
    Goals, design principles and some examples of using IFWIS Core
  • Core API
    Learn about the application programming interface (API) for interacting with our biological records.
  • Data Model
    Review a relationship diagram of how our data is stored.
  • Why Core?
    A plain english explanation of what's going on here.
  • Contact Developer
    Not working like it should? Please let us know.

Apps Built On Core