|
Q:
I
downloaded the tool, but got the following error message:
"Your Java VM needs to be upgraded (to Java 1.x.x) before
this program can be run..." What do I do?

Ans: The above message implies that JAVA Runtime Environment
is not setup in the machine or is of older version. Please
click here and follow instruction
given at the website to download and install JAVA Runtime
Environment (version 1.3.1 or later).
Q: The
DLNET LO tool started up fine, what do I do next?
Ans: Now you are ready to create the DLNET LO package.
Please follow the instructions either from the help menu or
the above guidelines to generate
the LO package.
Q: How
long does it take to create a DLNET LO package?
Ans: It depends on the total size of the resources
being bundled and the collection of metadata. Filling the
metadata form takes about 5 to 10 min while validation and
packaging depends on the total size of resources. It was noted
that for a 3 MB of HTML type resource, the validation process
took less than a minute. On average, it takes less than 10
minutes to create a DLNET LO package.
Q:
Do
I have to register with DLNET to submit my DLNET LO package?
Ans: Yes. Please register as a "Content Contributor"
at DLNET to submit the DLNET LO package created using the
tool. If you are already registered as General User or Reviewer,
please update your user status to be included as Content Contributor.
To register as DLNET Content Contributor, click here.
If you are already registered as "Content Contributor", please
login
to DLNET to submit the package.
Q:
Where
can I get more information on DLNET LOs? What are the metadata
and the packaging standards used in DLNET?
Ans: For more information on DLNET LOs including a
comprehensive definition and an example, click here
(pdf format). DLNET has adopted IMS's metadata and content
package schemes. Details of this can be found at the IMS website.
Q:
What
are the copyright restrictions on the resources once bundled
as a DLNET LO package?
Ans: DLNET LOs will have no copyright restrictions
unless explicitly indicated. However, the user is requested
to use the LO as is, i.e., with its metadata included, to
acknowledge authorship and ownership of the content.
Q:
I
start up a DLNET LO profile (either New or Existing), but
the tool hangs (for over 5 min). What happened?
Ans:
Once the profile is set, the tool attempts to determine the
path to all the resources within that folder. These are the
resources that are validated in STEP 3 and when successfull
are packaged in STEP 4. If the profile is set at a very high
folder level within Windows system (such as at DESKTOP) or
the number of folders and files within the top resource folder
is high (over 10,000 files with a combined size of over 15
MB) then the tool attempts to capture the path information
of these files. Due to limitations of the machine (either
the CPU speed or available memory) this large amount of data
causes application instability and the tool hangs. Kill the
DLNET LO Tool when this happens. The easiest way to avoid
it is to close some other applications currently not in use
(so as to free up system resources), then to re-start DLNET
LO Tool and re-try building the LO. More importantly, make
sure that the resource and all its component files and folders
are not on the desktop or other system folders but in a separate
folder of their own.
Q:
I
started up a DLNET LO profile (either New or Existing), but
the tool hangs (for over 5 min). I noted the memory and CPU
usage was very high. What happened?
Ans: Please see the answer to the prior question.
Q:
I
navigated to where my resource files are located and setup
the DLNET LO project filename (xx.dln, either New or Existing),
but the tool hangs (for over 5 min). What happened?
Ans: Please see the answer to the prior question.
|