| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
|---|
| 2 | <html xmlns="http://www.w3.org/1999/xhtml"> |
|---|
| 3 | <head> |
|---|
| 4 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
|---|
| 5 | <title>New DC</title> |
|---|
| 6 | <!--2010-06, History: Updated references to Guidelines; removed reference to future cloning; let's cross that bridge when and if we come to it. Removed reference to Type not being editable: it is actually editable, but that does change the nature of the DC.--> |
|---|
| 7 | <style type="text/css"> |
|---|
| 8 | <!-- |
|---|
| 9 | .style1 {color: #FF0000} |
|---|
| 10 | --> |
|---|
| 11 | </style> |
|---|
| 12 | </head> |
|---|
| 13 | |
|---|
| 14 | <body> |
|---|
| 15 | <blockquote cite="ISOcat Interface"> |
|---|
| 16 | <p align="left"><strong>New DC</strong></p> |
|---|
| 17 | <p align="left"><a href="dataCategorySpecification.html">Data category specification</a> creation function</p> |
|---|
| 18 | <p align="left">Click on "My Workspace" at the top of the browser pane to view the Workspace control bar. The "New Group", "New DCS", and "New DC" icons appear at the top of the DCS pane. Click on the New DCS icon to create a new <a href="dataCategorySelection.html">DCS</a> or on the New DC icon to create a new <a href="dataCategory.html">data category</a> in your <a href="Private.html">private space</a>. You can also simply add a new DC to your private space or to an existing DCS. Before adding a DC for the first time, please check out the specifications in the <a href="http://www.isocat.org/files/manual.html">DCR Guidelines</a>. The authority and credibility of the DCR depend on your careful compliance with basic naming and definition principles.</p> |
|---|
| 19 | <p align="left"><img src="CreateDCS_DC.jpg" alt="Create New DC" width="801" height="336" longdesc="CreateDCS_DC.jpg" /></p> |
|---|
| 20 | <h3 align="left"><a name="newDCS" /><span class="style1">Creating a new DCS</span></h3> |
|---|
| 21 | <p>If you choose to create a new DCS, the New DCS pop-up menu will appear. Enter a name for your DCS and select "Create".</p> |
|---|
| 22 | <p align="left"><img src="NewDCS.jpg" alt="Create New DC" width="336" height="336" longdesc="NewDCS.jpg" /></p> |
|---|
| 23 | <p>You can now add new DCs and save them to your new DCS. They will appear in the basket pane at the bottom of the screen. Or you can open other DSCs and select items to add to the new DCS in the <a href="basket.html">basket pane</a>. You can save new basket pane contents as desired.</p> |
|---|
| 24 | <h3 align="left"><a name="newDC" /><span class="style1">Creating a new DC</span></h3> |
|---|
| 25 | <p align="left">The New DC template is divided in three sections, reflecting the ISOcat data model. As you move through the template, tab from field to field in any given row. In the description section, use the blue plus sign to create new fields. Click in a new field in order to enter data.</p> |
|---|
| 26 | <h3 align="left"><a name="adminInfo" /><span class="style1">Administration Information Section, Identification</span></h3> |
|---|
| 27 | <p align="left">The first screen that appears is the <a href="AdministrativeInformationSection.html">Administrative Information Section</a>. The system assigns a non-mnemonic numerical identifier to your new DC when you save the specification. This numerical identifier forms the base for the non-mnemonic <a href="persistentIdentifier.html">persistent identifer</a> (PID) assigned to the DC. You begin your work by filling in the attributes in the Identification class. |
|---|
| 28 | <h3 align="left"><a name="identifier" />Identifier</h3> |
|---|
| 29 | <p align="left">The identifier is a mandatory field. Enter a unique <a href="camelCase.html">camel case</a> string in the Identifier field. It should be a meaningful name, such as the camel case form of the preferred English <a href="DataCategoryName.html">data element name</a>. It will be used together with the PID to access the data category both inside the DCR and as a reference from other external language resources. </p> |
|---|
| 30 | <p align="left">The identifier checker checks whether: |
|---|
| 31 | <ul> |
|---|
| 32 | <li>that identifier is a valid XML local name (see the <a href="http://www.isocat.org/files/manual.html">DCR Guidelines</a> for info on XML names);</li> |
|---|
| 33 | <li>that identifier already exists in your <a href="Private.html">private</a> workspace;</li> |
|---|
| 34 | <li>a DC with that identifier exists in the <a href="Public.html">public</a> space that you can use instead.</li> |
|---|
| 35 | </ul> |
|---|
| 36 | <p align="left">After you have checked out these options, if you still want to create the new DC (maybe you need a different <a href="definitionSection.html">definition</a>), the checker should display a green check mark and you can move on. If the data category definition in the existing field is the same as that for your DC, you can simply add your profile to the existing data category specification rather than creatin a new one. Check the <a href="profile.html">profile</a> page for instructions on how to do this. If you need a different <a href="conceptualDomain.html">conceptual domain</a> from the existing one, you can create it when you get to the Conceptual Domain section of the template.</p> |
|---|
| 37 | <h3><a name="version" />Version</h3> |
|---|
| 38 | <p align="left">The Version number is set to 0.0.0. If you keep this DC in your <a href="Private.html">private space</a>, it stays at this level. If you ever submit to a <a href="ThematicDomainGroup.html">TDG</a> for standardization and it is accepted as a standard DC, the version number will change.</p> |
|---|
| 39 | <h3 align="left"><a name="type" />(Data Category) Type</h3> |
|---|
| 40 | <p align="left">There are four kinds of data categories included in the DCR: |
|---|
| 41 | <ol><li><a href="complexDataCategory.html">complex data category</a> — <a href="openDataCategory.html">open DC</a></li> |
|---|
| 42 | <li>complex data category — <a href="closedDataCategory.html">closed DC</a></li> |
|---|
| 43 | <li>complex data category — <a href="constrainedDataCategory.html">constrained DC</a></li> |
|---|
| 44 | <li><a href="simpleDataCategory.html">simple data category</a></li> |
|---|
| 45 | <li><a href="containerDataCategory.html">container data category</a></li> |
|---|
| 46 | </ol> |
|---|
| 47 | <p>Select the desired data category type from the dropdown menu. Take care not to make an error because this categorization strongly affects the structure and behavior of your data category specification. It can be changed, however, but if you do that, check back through the entire entry carefully to make sure the specification is complete and correct.</p> |
|---|
| 48 | <h3 align="left"><a name="justification" id="type" /></a>Justification</h3> |
|---|
| 49 | <p align="left">The Justification field is mandatory. Enter the reason why this data category is important to a community of practice working with language resources. Make a clear statement because someone outside this community may not immediately see the relevance of the DC, especially if it is ever proposed for standardization. Do not repeat the definition here — just explain why the DC is useful. This can be simple: Used commonly in Terminology Management; present in ISO 12620:1999. </p> |
|---|
| 50 | <h3 align="left"><a name="origin" id="type2" /></a>Origin</h3> |
|---|
| 51 | <p align="left">State the source (document, project, discipline or model) for the data category specification.</p> |
|---|
| 52 | |
|---|
| 53 | <p><img src="NewDCStatus.jpg" alt="New DC Status" width="802" height="388" longdesc="NewDCStatus.jpg" /></p> |
|---|
| 54 | <h3 align="left"><a name="status" />Status</h3> |
|---|
| 55 | <p align="left">When you create a new DC specification in your private space, the administration status is set to -private- and remains at this setting, even if you change the <a href="Scope.html">scope</a> to -shared-. If, however, you choose to submit your DC to a TDG for standardization, this value will change accordingly as the DC passes through the standardization process, as indicated by the <em><a href="administrationStatus.html">Administration status</a></em>.</p> |
|---|
| 56 | <p align="left">The<em><a href="registrationStatus.html"> Registration status</a></em> indicates the status of the data category in the registration life-cycle.</p> |
|---|
| 57 | <h3 align="left"><a name="dates" />Dates</h3> |
|---|
| 58 | <p align="left">If you wish to set a range of dates indicating the validity of a particular DC, click on the Calendar icons to select your dates.</p> |
|---|
| 59 | <h3 align="left"><a name="additionalInformation" />Additional information</h3> |
|---|
| 60 | <p align="left">The additional information fields (<em>Explanatory comments</em> and <em>Unresolved issues</em>) provide space for the creators and editors of the DC to record notes on their work and document outstanding problems. These fields are not subject to any particular constraints and can be used as deemed fit.</p> |
|---|
| 61 | <h3 align="left"><a name="cancel-next" id="type3" /></a>Cancel/Next</h3> |
|---|
| 62 | <p align="left">Use <em>Cancel</em> to discontinue work on the DC, and <em>Next</em> to move on to the next section of the New DC template.</p> |
|---|
| 63 | <h3 align="left"><a name="descriptiveSection" /><span class="style1">Description section</span></h3> |
|---|
| 64 | <p align="left">The <a href="descriptionSection.html">description section</a> contains one or more <a href="languageSection.html">language sections</a> and one or more <a href="nameSection.html">names</a> assigned to the data category either in standards or in various working environments and communities of practice.</p> |
|---|
| 65 | <h3 align="left"><a name="profile" />Profile</h3> |
|---|
| 66 | <table width="904" border="0" cellpadding="2"> |
|---|
| 67 | <tr> |
|---|
| 68 | <td width="896"><img src="Check-Uncheck_Private.jpg" alt="Private Profile" width="801" height="344" longdesc="Check-Uncheck_Private.jpg" /></td> |
|---|
| 69 | </tr> |
|---|
| 70 | <tr> |
|---|
| 71 | <td><img src="CheckProfile.jpg" alt="PickProfiles" width="798" height="323" longdesc="CheckProfile.jpg" /></td> |
|---|
| 72 | </tr> |
|---|
| 73 | </table> |
|---|
| 74 | <p align="left">The default <a href="profile.html">Profile</a> value is <em>-private-</em>. Leave this profile value as is if you do not want to submit the data category specification for standardization at this time. If you want to declare it as part of an existing profile or profiles, click on the pencil symbol to open the picklist of values. Scroll down in the box and click in the selection box following the relevant profile name or names. If you do not want the <em>-private-</em> value to remain in addition to your selected profiles, you must unclick it. Click the green check symbol to close the dropdown box. For all simple data categories, be sure that the profile value is the same as that for the close data category with which they are associated. If this is not the case, the validation <a href="checkDC.html">checker</a> will register errors.</p> |
|---|
| 75 | <h3 align="left"><a name="descriptiveSection" />Data element names</h3> |
|---|
| 76 | <p align="left"><img src="AddDCName.jpg" alt="AddDCName" width="900" height="500" longdesc="AddDCName.jpg" /></p> |
|---|
| 77 | <p align="left">You can enter as many data element names as are relevant in the <a href="DataCategoryName.html">Data Element Names section</a>, including both the preferred name or names, as well as alternate names that are used in specific projects, other standards, etc. Be certain that the names you list all refer to the same <a href="DataCategoryConcept.html">data element concept</a> as reflected in the data category definition. This field is not mandatory, however, if you use it, you must add a source for each name, particularly any application or other resource that uses a specific name.</p> |
|---|
| 78 | <h3 align="left"><a name="languageSection" />Language section</h3><br /> |
|---|
| 79 | |
|---|
| 80 | |
|---|
| 81 | <table width="850" border="0" cellpadding="2"> |
|---|
| 82 | <tr> |
|---|
| 83 | <td><img src="DefinitionSection.jpg" alt="Language Section" longdesc="DefinitionSection.jpg" /></td> |
|---|
| 84 | </tr> |
|---|
| 85 | </table> |
|---|
| 86 | <p align="left">Enter at least one English <a href="DataCategoryName.html">data element name</a> in the English <a href="languageSection.html">language section</a> and indicate its status by clicking in the <em>Status</em> field and selecting a value from the drop down Status list; enter a properly documented data category definition in the English <a href="definitionSection.html">Definitions section</a>. Names and definitions should conform to the <a href="DCRGuidelines.pdf">DCR Guidelines</a>. Additional information should NOT be added to the <em>Definition</em> field. It can be entered in the <em>Example</em> or <em>Comment</em> fields.</p> |
|---|
| 87 | <p align="left">Click on <em>Language</em> along the right margin of the screen. Select the language from the pop-up list for any language sections you wish to add. If you do not find your language in the list of languages, contact the <a href="mailto:isocat@mpi.nl">ISOcat administration</a> with a request to add your language or languages. Theoretically at least any Unicode-enabled language can be added to the list. Fill in your target language equivalent for the data category name and the translation of the definition as you find it in the English language section. Be sure to include source information in the source field, as this becomes a mandatory field once you add information in the definition field for that language.</p> |
|---|
| 88 | <p align="left"><img src="LanguageSection.jpg" alt="Langguage Section" width="962" height="482" longdesc="languageSection.html" /></p> |
|---|
| 89 | <p align="left"> Enter examples, explanations, and notes as needed to further describe the data element concept or the way the data category is used.</p> |
|---|
| 90 | <h3 align="left"><a name="linguisticSection" /><span class="style1">Conceptual domain and linguistic sections</span></h3> |
|---|
| 91 | <p align="left">The default value for the conceptual domain is simply <em>String</em>, but you have a list of options to choose from. Note that <em>/grammar/</em> is a <a href="openDataCategory.html">complex open </a>DC, so you do not specify a value domain. </p> |
|---|
| 92 | <p align="left"><img src="ConceptualDomain.jpg" alt="Conceptual Domain" width="900" height="530" longdesc="ConceptualDomain.jpg" /></p> |
|---|
| 93 | <p align="left">To add simple data categories to the conceptual domain of a closed data category, click on the blue plus sign in the Conceptual Domain display and then click on your desired data categories in the DC Selector menu. Be careful to pick items that have been identifed as belonging to the same Profile as that of the Closed Data Category. (Conversely, be sure to declare any desired values as belonging to the appropriate Profile when you are working in the respective simple data category specifications.) Click <em>Select</em> to save the items you have selected.</p> |
|---|
| 94 | <p align="left"><img src="SelectDCConceptualDomain.jpg" alt="Select DC" width="900" height="560" longdesc="SelectDCConceptualDomain.jpg" /><em></em>:</p> |
|---|
| 95 | <p align="left">Your selected items will appear in the <em>Value Domain</em> window.</p> |
|---|
| 96 | <p align="left"><img src="ValueDomain.jpg" alt="Value Domain" width="900" height="310" longdesc="ValueDomain.jpg" /></p> |
|---|
| 97 | <h3 align="left"><a name="languageSection" />Save specification</h3> |
|---|
| 98 | <p align="left">Click the Save button in the lower right hand corner when you have completed entering all the data. Fill in any relevant change data in the Change description pop up and click Save. Unless otherwise assigned, you will find your new specification in the global DCS list for your Pivate workspace.</p> |
|---|
| 99 | <p align="left"><img src="SaveDC.jpg" alt="Save Info" width="799" height="305" longdesc="SaveDC.jpg" /></p> |
|---|
| 100 | <p align="left"> </p> |
|---|
| 101 | <p align="left"> </p> |
|---|
| 102 | </blockquote> |
|---|
| 103 | </body> |
|---|
| 104 | </html> |
|---|
