Each term has an identifier called a lid (language-id).   In the XML files, they are described as follows:


       lid="A1"  or clid="TCE1"


lids are collected into sets.  There is a set for the scoring terms of challenge A (chal_a).  Challenge A TDF terms are also a set (tdf_a).  There are also sets for common terms such as shared terms for expense reports (exp_common) .  To see the sets and the terms within each set, look in the Resource Area (Admin=>manage translation).  Each set is a row in the table displayed. Click on the icon for a set to see the lids in that set.


In the example above, lid specifies that the term is local to the set associated with this XML file.  So the lid A1 can be different for tech challenge and the arts challenge.  clid specifies a shared term across multiple XML files. 


For score sheets (scoring items), the lids are defined in the content file for a challenge.  For example b_2025_content.xml lists the lids and clids for Challenge B (scientific challenge for 2025).  Below is a segment of this .XML file.  All of these lids will be in the set chal_b since this segment is a part of the description of Challenge B. The value of each lid is as follows:


  • B = Scientific Demonstration
  • B1 = Integration of research about the science behind one specific, real phenomenon of the Planet into the Scientific Demonstration
  • B1-defn = This includes, but is not limited to, information about the one specific, real phenomenon and the scientific explanation for why that specific phenomenon happens and/or exists.
  • B2 =  effect of the Scientific Demonstration
  • B2-defn = This means the Scientific Demonstration is presented in a dramatic, interesting, and/or memorable way.


               <section title="Scientific Demonstration" lid="B">

                       <item type="subj" raw="30" detail="I.B" lid="B1">

                               Integration of research about the science behind one specific, real phenomenon of the Planet

                               into the Scientific Demonstration

                               <defn lid="B1-defn">

                               This includes, but is not limited to, information about the one specific, real phenomenon and the

                               scientific explanation for why that specific phenomenon happens and/or exists.

                               </defn>

                       </item>

                       <item type="subj" raw="30" detail="I.B" lid="B2">

                               Theatrical effect of the Scientific Demonstration

                               <defn lid="B2-defn">

                               This means the Scientific Demonstration is presented in a dramatic, interesting, and/or memorable way.

                               </defn>

                       </item>

               </section>

 


For online forms the lids are also defined in the XML files that describe the online documents.  process.xml (shown below) describes the creative process fields found in each of the challenge TDFs.  It has clids for the terms in this part of the TDF. clids (rather than lids) are used to place the lids in a common set (tdf_common in this case).  We also see another difference here: the lids have no name (eg clid="").  The .XML reader supplies the name as follows:


  • in a <part>
    • clid="" is the same as clid="<name>-title" and has a value of the title attribute
      so for the process part
      • clid process-title = Creative Process
    • clid_desc="" is the same as clid="<name>-desc" and has a value of the descriptive text between <part> and </part> 
      so for the process part
      • clid process-desc = Reflect on how your team experienced each stage of the creative process as you solved the Team Challenge.
  • in an <element>
    • clid="" is the same as clid="<name>" and has the value of the descriptive text between <element> and </element>
      so for the element recognize
      • clid recognize = RECOGNIZE: What process did your team go through in order to understand all the issues or points of the Challenge?


<part name="process" clid="" desc_clid="" summary_name="Creative Process" summary="1" 

               type="number-list" title="The Creative Process">

       Reflect on how your team experienced each stage of the creative process as 

       you solved the Team Challenge.

       <element type="para" clid="" max="1000" name="recognize" submit="info">

               RECOGNIZE: What process did your team go through in order to understand all the issues 

               or points of the Challenge?

       </element>

       <element type="para" clid="" max="1000" name="imagine" submit="info">

               IMAGINE: How did your team use your imagination to explore new ideas about possible solutions 

               to the Challenge?

       </element>

       <element type="para" clid="" max="1000" name="initiate" submit="info">

               COLLABORATE AND INITIATE: How did your team work in a collaborative way? How did your team take 

               risks and go beyond the minimum as you committed to a solution? 

       </element>

       <element type="para" clid="" max="1000" name="assess" submit="info">

               ASSESS: How did your team assess your solution as it was being created?

       </element>

       <element type="para" clid="" max="1000" name="evaluate" submit="info">

               EVALUATE AND CELEBRATE: Reflect on your experience. What did your team learn? How did your 

               team celebrate your journey and accomplishments?

       </element>

</part>


lids/clids are stored in the Resource Area's database.  There is a table of lids.  There is also a table that list each language's text for each term.


When you look at the translation page in the Resource Area, all the lids are grouped by translation set.  Diving down into a translation set shows its terms and the translations for that term.


The XML files that contain the lids are processed differently for score sheets and online forms.  The score sheet generator actually reads the XML files that describe the score sheet on the fly when generating the sheet.  As we need to do the translations before the generation occurs, we need a means of scanning the score sheets for lids.  The Scan Score Sheets button on the translation page (Admin=>manage translations) does this.


Online forms are stored as records in the Resource Area's database.  The lids are created at the same time the records are created. The Scan LiveDoc button on the translation page (Admin=>manage translations) will also do this..