Re: Recombo: Any need to build our own tool?

Author:

Raymond Yee

Posted:

5/15/2002; 5:30:27 PM

Topic:

Recombo: Any need to build our own tool?

Msg #:

451 (in response to 450)

Prev/Next:

450/452

Reads:

2162

Yes, I've been in contact with folks from Recombo. I sent email to technology@recombo.com asking for more specifics concerning Recombo Constructor. Very soon after, Brad McFee wrote back. With his permission, I post his email:

Hi Raymond,

Thanks very much for your enquiry. I would be interested in finding out more about what kind of digital resources your project involves to see how we can help but I thought I would start by answering your first question of what Recombo Convertor can do. Seeing as you are a techie yourself I thought I would give you a bit of a workflow for Recombo Convertor:

1. user can create a new project
2. user can import any structured source document (structure being a table
of contents) in a rich text format

Convertor will automatically:

convert it to the Recombo XML format

parse and chunk the content based on the original document structure (the above takes only seconds)

The software then allows the user to perform several key functions:

View and edit the tree (join objects, unjoin, group, ungroup, promote and demote) without ever breaking SCORM rules.

Add and edit metadata at the Aggregate, SCO or Asset level (as defined by SCORM www.adlnet.org).

Recombo Convertor also provides export functionality (the demo version has restricted functionality and only allows as a complete SCORM manifest as opposed to individual objects or asset export) to a file or repository so it can be viewed and/or served using a learning management system or SCORM viewer.

Our product demo launch is actually tomorrow and I would be happy to put you our list for product download if you would like. Does this answer your question? Is there more information I can provide or specific technical
questions I could get answered for you?

Regards...

The opinions or statements expressed herein should not be taken as a position of or endorsement by the University of California, Berkeley. Nor should the opinions or statements expressed herein be taken as a position of or endorsement of the University of California, Berkeley. Links on these pages to commercial sites do not represent endorsement by the University of California or its affiliates.