Hi Yushan,
I am having difficulty getting the IMS-CP imports to render in the
UI.
Using the Add Content-->Upload Content dialog, I can get an IMS-CP
item to upload and be processed by your code in IMSCPFileHandler.
I can then see the item in the explore Content list of content but
when I click on it, I do not get the hierarchical page structure. It
looks like I just see the first or top level page.
As your code says it is creating a course from the CP, I might expect
to see it the the Explore Courses list of courses but I do not. I
believe this may be because the code is not adding the property
category=courses so the groups_all search is not finding it.
I also thought it might appear in the list of sakai documents shown in
the "add a new area"-->"existing document" dialog in a Course world.
However, it does not appear in that list either, likely because is
does not have the _mimeType property set to x-sakai/document so the
all_all.json search for sakai documents doesn't find it. I notice
your code in the IMSCPFileHandler, at line 170, explicitly removes
that property. Why is that property being removed?
Can you give me any help on what work flow I should be using to render
an uploaded IMS-CP? Or any other assistance that might explain why I
can't get the package to do the full hierarchical rendering of itself
in the UI? What steps do you go through in the UI? Maybe I am
missing something obvious.
For the rendering, I assume that the key client side files and
lhnavigation.js and entity.html. Is this correct or should I be
looking elsewhere in addition?
Thanks in advance for your help.
John K.
On Aug 31, 4:01 am, Yushan <
lysha...@gmail.com> wrote:
> Hi, Jon, thanks for your suggestion, I'll try them.
>
> Yushan
>
> On Aug 31, 4:19 am, Jon Gorrono <
jpgorr...@ucdavis.edu> wrote:
>
>
>
>
>
>
>
> > Hi Yushan,
>
> > WRT ... examples of content packages, maybe you've already tried this
> > but it might be helpful to try some of the packages under the Content
> > Examples for SCORM 2004 4th since it uses CP v1.1.4
>
> >
http://www.adlnet.gov/capabilities/scorm/scorm-2004-4th
>
> > One valuable goal would be the ability to import without getting
> > flummoxed by SCORM extensions.
>
> > Moodle has a long list of content creator tools too... some of them
> > have also passed compliance tests at one point or another as well..
> > but after a quick scan of this list I can't say a tool that would be
> > both compliant and able to produce 1.1.4 CP files popped out at me:
>
> >
http://docs.moodle.org/20/en/Creating_SCORM_Content#Tools_for_Authoring
>
> > And if you've not done so already, maybe you can hazard employing the
> > Reload Content Packaging Tool from adl.... it's also listed on at that
> > page @ the url for
adlnet.gov above. It's not always clear what you
> > are doing with that tool sometimes, but it might prove useful to you.
>
> > On Tue, Aug 30, 2011 at 3:10 AM, Yushan <
lysha...@gmail.com> wrote:
> > > Hi, John,
> > > I implemented importing and exportingIMS CPin the last two months, I
> > > would like to
> > > explain the steps of importing and exportingims cpfiles in the
> > > program first:
>
> > > a) Import cp files
> > > 1) User choose zip files to upload
> > > 2) Program would scan whether there is imsmanifest.xml file, if it
> > > contains that file, it would
> > > be changed to sakai-doc type.
> > > 3) And then program would parse the xml file as a tree structure, if
> > > an item's resource
> > > is text type or directory node, the item would be add to the tree
> > > structure.
> > > 4) If the resource contains local link in its content, it would
> > > changed to our system path, for
> > > example, if there is "images/1.jpg" in the resource, this link would
> > > be replaced by "/p/image_id"
> > > 5) UI would display the file as sakai docs, and user can also download
> > > the origin zip file from
> > > the top.
>
> > > b) Export cp files
> > > Exporting cp files means exporting sakai docs asIMS CPfiles. There
> > > bundle, it doesn't supportims cpextension classes(ipointer, variant,
> > > lingualTitle) now.
> > > 2) I don't think there is much remaining work now, but I really think
> > > we need more examples for testing, I only got two
> > > Meleteims cpfiles from Ian, and I wrote test examples in lom and
> > > content-packaging bundles, but I think we need more actual
> > > examples.
> > > 3) Sure, glad to work with you:) I am an academic visitor in
> > > Cambridge(I am a graduate student in Tsinghua University),
> > > and I am going back this Thursday, but I think I would continue sakai
> > > work as a part time job since John Norman ask me to
> > > continue.
> > > 4) One reason is I didn't know there is LOM API... the other is cp
> > > files from Melete are not strictly standard. For example,
> > > langstring element in melete files is <langstring>content</
> > > langstring>, and its standard binding is <langstring><string>content
> > > </string><lang>en</lang></langstring>; source and value elements in
> > > vocabulary element are CharacterString type in IEEE lom,
> > > but in Melete files, they're langstring type. That also why I said we
> > > need more actual test examples.
> > > 5) I think we should add headers as sakaiproject requires, and I can
> > > do that.
>
> > > Yushan
>
> > > On Aug 30, 12:57 am, johnk <
johnfki...@gmail.com> wrote:
> > >> Hi Foks particularly Yushan,
>
> > >> Zach has asked me to look into the state of our development to support
> > >> import and export of IMS Content Packages, akaIMS-CP. Based on the
> > >>IMS-CP& LOM spec docshttp://
edutechwiki.unige.ch/en/IMS_Content_Packaginghttp://www.imsglo...