Create Serial Issue Record

POST /api/.../serialissues

Create serial issue record.

Request Information

Parameters
Name Type Required Description
dto DtoSCSIssueUpdateInfo Yes Define this parameter in the request body.
ignoreWarnings Boolean No Optional query string value. Default is false. Will skip validation warnings that the user can bypass.
DtoSCSIssueUpdateInfo
Property Type Nullable Description
CopyID Int No The unique id assigned to the serial copy record.
PubPatternID Int No The unique id assigned to the publication pattern.
NoteNonPub String Yes Non public note
NoteStaff String Yes Non-public/warning note
TitleOfSupIndex String Yes Title of supplementary material/index.
ExpectArrivalDate DateTime Yes Date Issue/Part is expected to be received by library. This date is calculated based on record's ChronologyDate and its linked publication pattern's arrival pattern.
ChronologyDate DateTime Yes Chronology date of the Issue/Part record. This date is converted from the chronology values of the issue/part record by Polaris.
Designation DateTime Yes Issue/Part's designation.
BibliographicRecordID Int Yes Part record linked bibliographic record control ID. For an Issue record, this field should always be NULL.
UnitPrice Decimal Yes Unit price of an individual issue/part
IssueStatusId Int Yes ID of issue's current status
ClaimReasonID Int Yes ID number of claim reason
Response string Yes A free text field for users to add a note regarding a response from the supplier to a claim for an item.
Reminder boolean Yes Bit flag that displays in the Claim Alert List (CAL) when the item appears there.
ClmNote string Yes A free-text note associated with a claim
SSOChronList Array of DtoSerialIssueRecordChronology Yes Array of issue record's chronology.
SSOEnumList Array of DtoSerialIssueRecordEnumeration Yes Array of issue record's enumeration.
Example
application/json, text/json 
 {
  "CopyID": 1,
  "PubPatternID": 1096,
  "ExpectArrivalDate": "2021-03-02T20:00:08.752Z",
  "NoteNonPub": "Non public",
  "NotePub": "Public Note",
  "NoteStaff": "Staff Note",
  "ChronologyDate": "2021-03-02T20:00:08.752Z",
  "Designation": "(2011)",
  "TitleOfSupIndex": "Title Of Sup Index",
  "BibliographicRecordID": 0,
  "UnitPrice": 3,
  "IssueStatusId": 2,
  "ClaimId": 0,
  "ClaimReasonID":1,
  "Response": "Claim Response",
  "Reminder": true,
  "ClmNote": "Claim note is added",
  "SSOChronList": [
     {
        "ChronCap": 1,
        "LevelNum": 1,
        "IsAlter": false,
        "FormatID": 1,
        "ChronValue": "2003"
      },
      {
        "ChronCap": 4,
        "LevelNum": 2,
        "IsAlter": false,
        "FormatID": 3,
        "ChronValue": "01"
      }
  ],
  "SSOEnumList": [
    {
        "LevelNum": 1,
        "IsAlter": false,
        "EnumCap": "Vol.",
        "FormatID": 1,
        "BibUnits": 0,
        "NumSchemeID": 0,
        "EnumValue": "44"
      },
      {
        "LevelNum": 2,
        "IsAlter": false,
        "EnumCap": "No.",
        "FormatID": 1,
        "BibUnits": 11,
        "NumSchemeID": 1,
        "EnumValue": "1"
      }
  ]
}

Response Information

ID of newly created issue record is returned upon success.

Example
application/json, text/json 
21584

HTTP Response Codes

Code Description
200 OK. Success
400 FAILURE. Invalid Copy ID.

Required Permissions

Permission IDs found here.

    CR_AccessSerials_Allow
    CR_SerialIssuesStandingOrderParts_Create (based on destination org ID)