Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

The signature will have the following format:

[mmttttvv]
Where:

mm: is a two letter code denoting the maker of the tool
tttt: is a two to four letter code denoting the name of the tool
vv: is a two digit code indicating the major and minor version of the tool
For example, the survey tool produced by lams has a signature of lasurv10. The "la" indicates that it was developed by the main LAMS team, "surv" stands for "survey" and "10" indicates that it is version 1.0.

We are trying the ensure these codes are unique to each person/company/institution/etc but if we need to double up it won't be fatal as it is the combination of "mmtttt" that needs to be unique. LAMS doesn't split up the tool signature into its parts and assign them any meaning so if we start running out of codes we can switch to "mmmttt".

The tool's tables in the database should be named tl_<signature>_<rest of name>. For example, a survey tool table is tl_lasurv10_survey_content. _The signature is kept short to allow the database table names to be short. See Tool Database Considerations <rest of the name> to be meaningful and yet be compatible with databases that allow 32 character tablenames. See Database Conventions and Datasources for more information.

The jar and war files for the tool must also use the signature. So the jar and war files for the survey tool are lasurv10.jar and lasurv10.war.

When you start developing a tool, please contact the Wiki Sysops Fiona Malikoff or Ernie Ghiglione to reserve your tool signature.

Existing Tool Signatures

Developed by the core LAMS team:

Chat lachat11
Forum lafrum11
IMS Content Package Display laicp10
Multiple Choice lamc11
Noticeboard lanb11
Question and Answer laqa11
Resources larsrc11
Scribe lascrb11
Submission lasbmt11
Survey lasurv10
Voting lavote11

. They are "11" for 1.1 - LAMS 2.0 was originally going to be LAMS 1.1 and we had already determined the signatures when we changed the version to 2.0.

Assessment

laasse10

Chat

lachat11

Data Collection

ladaco10

Dimdim

laddim10

Example

laex11

Example tool used as starting point for new tools. Not included as an usable tool in production.

Forum

lafrum11

Google Maps

lagmap10

Images

laimag10

Mind Map

lamind10

Multiple Choice Questions

lamc11

Notebook

lantbk11

Noticeboard

lanb11

Pixlr

lapixl10

Question and Answer

laqa11

Share Resources

larsrc11

Share URLS, files, websites and learning objects.

Scribe

lascrb11

Write a group report with one learner as the scribe.

Submission

lasbmt11

Submit a file to the teaching staff for marking.

Survey

lasurv11

TaskList

latask10

Video Recorder

lavidr10

Voting

lavote11

Wiki

lawiki10

Maker Codes

The following maker codes are either used or reserved for someone working on a tool.

mm

Group using the code

kk

 

la

Core LAMS team

Date Based Tool Version

When you create your tool entry, you find you also need to supply a version in the format YYYYMMDD. This is used for installation scripts to update your database and by the import/export logic to convert any old export files to a version compatible with the "current" version of your tool.

It is very important that you stick to this format for the lams_tool.tool_version column. LAMS will work initially if you use a different format, but there will be problems for your users in the future when you produce a new version. We would like to think your tool will be so popular that you will want to bring out new features for your tool and hence new versions.

This version does not have to match the vv in the tool signature. The vv in the tool signature should match something meaningful for your users.