My customer has specific requirements about the contents of the course metadata files. I have to publish in SCORM 2004, 4th Edition. I have an enormous checklist of standards against which to verify my course output. Does anyone have experience manipulating or modifying the format/contents of metadata produced by Storyline 360? For example, I'm required to have a file with the name "course_metadata.xml" in the root folder of the course package...by default (in 2004 SCORM Ed. 4), Storyline 360 generates a file named "metadata.xml" in the root folder. Can I just rename the file and then make the corresponding update to the imsmanfest.xml?
You can, but what if you need metadata.xml? I would copy it, then rename it and edit the copy. As far as updating the manifest, I would look to their requirements for guidance on that.
Just my personal opinion: this sounds like a real pain, and a bunch of work after the course is finished and published. I hope your rate and/or time scope represent the extra effort.
That's a great idea, Walt, thank you!! And I agree with you entirely about the fact that it's a pain, but yes, going into the project I knew there were probably standards I had to abide that would be extraneous and arbitrary and impossible to avoid. The course aesthetic design didn't get much attention because of the level effort I knew had to be expended during publishing to meet weird requirements like these.
2 Replies
You can, but what if you need metadata.xml? I would copy it, then rename it and edit the copy. As far as updating the manifest, I would look to their requirements for guidance on that.
Just my personal opinion: this sounds like a real pain, and a bunch of work after the course is finished and published. I hope your rate and/or time scope represent the extra effort.
That's a great idea, Walt, thank you!! And I agree with you entirely about the fact that it's a pain, but yes, going into the project I knew there were probably standards I had to abide that would be extraneous and arbitrary and impossible to avoid. The course aesthetic design didn't get much attention because of the level effort I knew had to be expended during publishing to meet weird requirements like these.