Re: AW: ZMS content -> SCORM export

Niels Dettenbach <[email protected]> Wed, 24 Nov 2010 18:04:07 +0100
Newsgroups gmane.comp.cms.zms.devel
Organization Syndicat IT&Internet
Message-ID <[email protected]>
Am Samstag 13 November 2010, 11:22:42 schrieben Sie:
> Hello, please start with using the ordinary html-Export to get the rendered
> pages. The imsmanifest file will be included.
> Best regards
> fh
Many thanks for this hint - this was very helpful.

In the meantime i worked out a set of templates and configurations which 
allows to export folders ("ordner") recursively into SCORM / HTML.

This works really nice, but i have a prob with including stuff (the "common" 
folder) from the main ZMS instance.

I have a parent ZMS instance (where i have placed the usual "common" folder 
for all subinstances) and several subinstances of ZMS with differing CSS / 
template sets (within a "instance" folder).

If i export a folder within a ZMS subinstance into static HTML i did not get 
the required content from the common folder within the parental ZMS instance 
(which works nice within ZMS as usual).

I tried to set:

	ZMS.export.domains
to
	common

but this did not include the common folder (incl. content) to my exports. If i 
copy the common folder into the ZMS-root of the subinstance it works as 
expected (but i want to have only a single "common" - not a copy in every 
instance).

As far as i understand ZMS.export.domains allows to include any other "ZMS 
instance" into the export output (and "common" seemed to be pre-defined). So i 
tried the name of the master/parent instance and or things like 
"master.common" or "master/common" which won't work too.

Is ZMS.export.domains the correct parameter to include further resources (i.e. 
folders). Does the ZOPE aquisition works here too?

How can i get additional folders (i.e. used by aquisition) into the exports?

If this is not possible in the current - does it makes sense for me to write a 
own function into the ZMS core which allows addition of aquisition folders 
into the exports (i.e. by a configurable list, 1-dim array)?


Many thanks for any hint.


best regards,


Niels.


> 
> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:[email protected]]
> Im Auftrag von Niels Dettenbach
> Gesendet: Freitag, 12. November 2010 17:32
> An: [email protected]
> Betreff: [zms-developers] ZMS content -> SCORM export
> 
> Dear all,
> 
> 
> currently i'm trying to export ZMS content as SCORM compatible packages.
> 
> Is there any howto, filter or other direction how a export to SCORM
> (content only, no tracking nor lms) could be done? SCORM export is
> described as a feature on many ZMS related pages, but there is no word how
> this could be done.
> 
> If not, does anyone can give me some directions how to get a suitable
> filter working?
> 
> The "content packages" should be imported into other SCORM compatible LMS.
> 
> Many thanks for any point or hint.
> 
> 
> best regards and a nice weekend to all here,
> 
> 
> Niels.


-- 

---

  Niels Dettenbach
  ---
  Syndicat IT&Internet
  http://www.syndicat.com
  T.-Muentzer.-Str. 2, 37308 Heilbad Heiligenstadt - DE
  ---
  Kryptoinfo: 
  PGP public key ID 651CA20D
  Fingerprint: 55E0 4DCD B04C 4A49 1586  88AE 54DC 4465 651C A20D
  https://syndicat.com/pub_key.asc
  ---
signature.asc (application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iQIcBAABCAAGBQJM7UWLAAoJEM78prARigUnIR0P/RReWYAa8qCLnSG8HRVTsx/s
DGZiZxGCspVFq2NlGcBaeX0SflS6iGt7FpwePtpg07Ji+GqqjNCCro0mT5YkFs2J
Of/xYzZppGrE/OKCoE1UcisVzdm6zF4bXHiLtaqvqhBcPUl/jW89ke+RH8Iidjum
WfwmUM63vYBHlDWeRhH6G/29vq9856hFhH7uTlwRdXQGxhaNnFDpKD1YrpIDd9GH
OZSvZBmFdHVmnzgIT1I5rEAahCUzmx1YmlIpTyRBvuA5BZKoQKajmHJ9N17CzZWM
X8jzPUwVpkekLg44iCizOaCCbjrPuVU0DRxU/TT9bqC+md0UZXO4A4Jw48UJwOR/
96JV1/Zl6nCt17AztsmrIq6iFVBTPzLhailRFf8EHQCfXImVYnTfMEnUqmMnBWNs
8ZsW16bWN0pecK/1YiH1YwNgr5LQCX87faCIhENPt2jBlKtbBNQpUgn0GkNcGLEw
W/ETm7veAEwm4KV0P/tG2O8D9p9S7jDQN5DGd0nLaM5y6LbICMowJ8N6Q2J3pTO9
DnA6T/g51Q8ICyiQWEmFZdr8KJ1ad9cppG08B9Qf661i6gEFa6BkA9wNSUY/uyv4
YKHhGtC68nPg7g3vA20DERaHVHCpaxCYDZSuHCfDLqpXpqlYAknnquDV7coXLitZ
32+uqs4xBV1RO2+iX/4C
=P4dx
-----END PGP SIGNATURE-----