PREVIOUS VERSION

This site is the documentation for a Scholar Snapp Austin (v3.0), a previous version of the Scholar Snapp Technology Suite.

The Snapp solution is currently backward-compatible with v3.0, but all new development projects should leverage Scholar Snapp Technology Suite Berkeley (v4.0).

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

The final draft of the Scholar Snapp v3.0 data standard for the 2017-2018 application cycle was published on May 15, 2017. The Snapp Central API currently accepts and emits Snapp v2.0, the previous version. Development on the Snapp Central API to accommodate v3.0 is in progress (ETA July/August 2017). We encourage all new integrators to use v3.0.

Overview

The Snapp Data Standard XSD supports the inclusion of file attachments in the AttachedFiles entity. Providers can use this construct to include files commonly found in scholarship applications such as a transcript, a portrait of the student, and so forth.

The AttachedFiles entity is optional and the Snapp XSD supports 0-n attachments.

File Size

The Snapp XSD specifies no technical limits on the number or size of attachments. This raises an issue for API implementers. If the overall Snapp XML data file can contain multiple files and/or very large files, system designers have to consider issues like resuming dropped connections

The Snapp community, and the Snapp Central API addresses these issues by convention.

  • The Snapp Central API does not send attachments by default. Implementers MUST provide the header value to the Snapp Central API when receiving a file. Implementers MAY implement the same behavior when sending files to Snapp Central. Snapp Central will be prepared to accept attachments in any exchange, so this is optional.
  • Snapp Central limits individual file sizes to XX and the overall Snapp XSD file to YY. Implementers that interact with Snapp Central MUST to do the same when sending to Snapp. Implementers SHOULD do the same if they support transfer with other organizations. 


Details

This section contains detail and usage notes about the elements in the Context entity:


  • No labels