SCORM Manifest SCORM Manifest AWS
SCORM Manifest Proper Formation Another integral part of the content package delivery is a well formed and simple IMS Manifest. The IMS Manifest is the list and organization of the elements in a SCORM package. This important XML formatted file tells the SCORM player how to organize the learning items as well as a punch list of all items in the course package. Further, it contains a unique identifier for the content and a parent child relationship showing the individual SCOs. The VWGoA / VGCA LMS only supports single SCO learning items. If you need to break up the content into logical pieces, please do it at the presentation layer of the course. Most off the shelf e-learning content creation tools allow a great deal of flexibility when it comes to creating an IMS Manifest. However, there are some LMS implementations that would react unfavorably to some of the free form metadata elements of the IMS manifest data structure. In regards to the VWGoA / VGCA LMS: •
The manifest identifier must not start with a number, only alpha characters.
•
The Organization and Organizations s tag must have an IDENTIFIER and DEFAULT that is less than 10 characters and also must not start with numbers.
Lastly, the IMS manifest (imsmanifest.xml) file MUST be in the root of the packaged content.
SCORM Manifest File Naming A common issue that is see is the use of illegal characters within filenames and manifest entries. Your web files will be viewed by numerous users who use a wide variety of operating systems (Mac, PC, and Linux for instance) and devices (desktops, tablets, and smartphones are some examples). Therefore, it is essential to play it safe and avoid common illegal directory and filename characters. Naming conventions are important in web folders as well as for downloadable files such as PDFS, Word documents, and Excel spreadsheets. Do not use any of these common illegal characters/symbols: # pound
< left angle bracket
$ dollar sign
+ plus sign
% percent
> right angle bracket
! exclamation point
` backtick
& ampersand
* asterisk
‘ single quotes
| pipe
{ left bracket
? question mark
“ double quotes
= equal sign
} right bracket
/ forward slash
: colon
\ back slash
blank spaces
@ at sign
Also, keep these rules in mind. • • • •
Don’t start or end your filename with a space, period, hyphen, or underline. Keep your filenames to a reasonable length and be sure they are under 31 characters. Most operating systems are case sensitive; always use lowercase. Avoid using spaces and underscores; use a hyphen instead.
Bad filenames: • •
F&A Costs.html my PDF file#name.pdf
Web Browsers see: • •
F&A%20Costs.html my%20PDF%20file%23name.pdf
The manifest identifier must not start with a number, only alpha characters.
•
The Organization and Organizations s tag must have an IDENTIFIER and DEFAULT that is less than 10 characters and also must not start with numbers.
Lastly, the IMS manifest (imsmanifest.xml) file MUST be in the root of the packaged content.
SCORM Manifest File Naming A common issue that is see is the use of illegal characters within filenames and manifest entries. Your web files will be viewed by numerous users who use a wide variety of operating systems (Mac, PC, and Linux for instance) and devices (desktops, tablets, and smartphones are some examples). Therefore, it is essential to play it safe and avoid common illegal directory and filename characters. Naming conventions are important in web folders as well as for downloadable files such as PDFS, Word documents, and Excel spreadsheets. Do not use any of these common illegal characters/symbols: # pound
< left angle bracket
$ dollar sign
+ plus sign
% percent
> right angle bracket
! exclamation point
` backtick
& ampersand
* asterisk
‘ single quotes
| pipe
{ left bracket
? question mark
“ double quotes
= equal sign
} right bracket
/ forward slash
: colon
\ back slash
blank spaces
@ at sign
Also, keep these rules in mind. • • • •
Don’t start or end your filename with a space, period, hyphen, or underline. Keep your filenames to a reasonable length and be sure they are under 31 characters. Most operating systems are case sensitive; always use lowercase. Avoid using spaces and underscores; use a hyphen instead.
Bad filenames: • •
F&A Costs.html my PDF file#name.pdf
Web Browsers see: • •
F&A%20Costs.html my%20PDF%20file%23name.pdf
