Recent Changes

Wednesday, October 18

  1. page Sumero-Akkadian edited ... šar-ru, šarru, “king” ḫu-ra-ṣú-um, ḫurāṣum, “gold” ... of a word. BAN, word: BAN, “bow…
    ...
    šar-ru, šarru, “king”
    ḫu-ra-ṣú-um, ḫurāṣum, “gold”
    ...
    of a word.
    BAN,
    word: BAN, “bow” i.e. the weaponweapon.
    (Behind this reading lies a grammatical expression of the word qaštu.)
    A phonogramphonetic complement can be
    ...
    the scribe intended, and which grammatical form.
    BAN-tu,
    intended: BAN-tu, which would
    A determinative is a sign that marks the semantic class of the word of which it is a part. Examples of typical semantic classes include, material, animal, vocation, and geographic element. There are only a few dozen determinatives. The determinative sign can occur at the beginning or end of the word. When transcribed, a determinative is usually superscripted. There is no consistency of capitalization across various transcription traditions. There is usually no space between the superscripted determinative and the adjacent transcription. For the purposes of text importation into OCHRE specifically, a space indicates a word separator. Therefore, a determinative should not be separated by a space.
    GIŠBANMEŠ, “bows”
    (view changes)
    10:00 am
  2. page Sumero-Akkadian edited ... DUMU níq-me-pa LUGAL URUú-ga-ri-itKI Note that the transcription given to the database does n…
    ...
    DUMU níq-me-pa LUGAL URUú-ga-ri-itKI
    Note that the transcription given to the database does not contain additional codes that would serve to markup the document. There are no complex prefixes to set off words or lines. Further, there are no tags or elements to define or classify the content. These cumbersome elements are removed from the interface. Instead, the import tool uses project-level specifications to ingest the formatted transcription. This strategy allows the researcher to import already existing transcriptions from their own files or from other sources, with very little technical formatting.
    {fig_01_transcription_options.png}{Text_config.JPG}
    Figure 1 – Transcription Options
    The user can load or copy from a formatted document (like Word .docx) and paste into OCHRE. Alternately, transcriptions can be typed directly into a pending content pane from which the import tool will ingest the textual data.
    (view changes)
    9:49 am
  3. file Text_config.JPG uploaded
    9:49 am

Tuesday, October 17

  1. page Agnostic Variables edited ... To override the standard unit default on data entry, simply enter the numeric value along with…
    ...
    To override the standard unit default on data entry, simply enter the numeric value along with an approved compatible unit; for example, "5 cm". Approved units are those that match either the full name of the Variable as listed in the OCHRE Measurements hierarchy, or any of its abbreviations. If a unit other than the base unit is specified, this also has the effect of changing the default unit going forward for the current session. That is, if a user enters a Length of "5 cm" and saves this value for the current item, on the next item if the user enters "6" it will be assumed that this is "6 cm" (having established a new default unit). To revert to the default base unit simply provide it explicitly, e.g. "0.1 m".
    By way of explanation, under the hood OCHRE will retain the data as it was entered so as not to lose the original content. But it will also calculate the equivalent standard value on-the-fly and will save this as well (as a ghosted value not visible to the user). This standard value is then available to be used for comparisons and calculations that require values to be normalized into values of same units. If the original value is edited the compatible standard value will also be updated; the two will always stay in sync.
    Querying Using Agnostic Variables
    Agnostic variables participate very naturally in OCHRE queries in the usual way. Specify the units if needed, e.g. Length is greater than 5 cm, or omit the units altogether to query based on the standard unit. OCHRE will do the necessary conversions and comparisons behind the scenes and will report all results whether they were originally entered in centimeters, meters, millimeters, or even inches.

    Other Uses of Agnostic Variables
    Having originally conceived of the use of agnostic variables for managing measurements, we are finding it to be extremely useful for managing currencies as well, both modern and ancient. One of our projects that tracks the sale of ancient artifacts on modern-day markets can enter price-based data as USD, EUR or GBP, depending on the source of the sale. Another project studying the coins found in hoards all over the Greek world tracks currencies based on staters and tetradrachms. This is obviously a more complex usage since currency values fluctuate with respect to other currencies over time. But the basic strategy works well, and we are working on ways to dynamically adjust the relevant conversion factors as needed in different circumstances (e.g. on a query or view).
    (view changes)
    9:57 am

Saturday, October 14

  1. page Version updates 2017 edited 2017-04-19 Variables/Values Introduced Derived special-purpose Variables for ... Concatenatio…
    2017-04-19
    Variables/Values
    Introduced Derivedspecial-purpose Variables for
    ...
    Concatenation, Conversion, Selection, and also Selection.Substitution. For details,
    ...
    uses, see Derived Variables.
    2017-10-15
    Query/Sets
    (view changes)
    4:34 pm
  2. page Version updates 2017 edited 2017-04-19 Variables/Values Introduced Derived Variables for Aggregation, Calculation, Concatena…
    2017-04-19
    Variables/Values
    Introduced Derived Variables for Aggregation, Calculation, Concatenation, Conversion, and also Selection. For details, and for examples of their uses, see

    2017-10-15
    Query/Sets
    (view changes)
    4:32 pm
  3. page Version updates 2017 edited ... Query/Sets Fixed long-outstanding bug of not saving uncertainty on Query property Criteria. …
    ...
    Query/Sets
    Fixed long-outstanding bug of not saving uncertainty on Query property Criteria.
    ...
    options. See >>>Finding Co-occurrences of Words Within Texts for details.
    Added an option under Format Specifications to split (multiple) Notes into separate columns. If Note Labels have been used to identify the notes, these will be used as column headings, otherwise the notes will simply be numbered. For example, here is a strategy often used for legacy data:
    {2017_SetSplitNotesII.PNG}
    (view changes)
    3:27 pm
  4. page Version updates 2017 edited ... Query/Sets Fixed long-outstanding bug of not saving uncertainty on Query property Criteria. …
    ...
    Query/Sets
    Fixed long-outstanding bug of not saving uncertainty on Query property Criteria.
    Adjusted the Components link option of Concepts to allow grammatical forms and attested forms (not just lemmas), and adjusted the Query to handle these options. See >>> for details.
    Added an option under Format Specifications to split (multiple) Notes into separate columns. If Note Labels have been used to identify the notes, these will be used as column headings, otherwise the notes will simply be numbered. For example, here is a strategy often used for legacy data:
    {2017_SetSplitNotesII.PNG}
    (view changes)
    3:24 pm
  5. page Version updates 2017 edited 2017-10-15 Query/Sets ... uncertainty on query Query property criteria. Criteria. Added a…
    2017-10-15
    Query/Sets
    ...
    uncertainty on queryQuery property criteria.Criteria.
    Added an option under Format Specifications to split (multiple) Notes into separate columns. If Note Labels have been used to identify the notes, these will be used as column headings, otherwise the notes will simply be numbered. For example, here is a strategy often used for legacy data:
    {2017_SetSplitNotesII.PNG}
    The Split notes option will generate this effect in the Table view:
    {2017_SetSplitNotes.PNG} Notes split into separate table columns with their Note Labels as headers
    Added an option under Format Specifications to Split values/units for units-enabled properties. Along with the original units-enabled value, this option will also create columns for the base value (as resolved to the standard unit) and its standard unit. This produces a table with columns of numeric values uncomplicated by their units-designations (which are strings). That is, "50 g" is resolved to: "50 g", "50", "g", "0.05", "kg".

    Variables/Values
    Added an option to request a pick-list for Alphanumeric Variables, both when doing data-entry of an item's Properties pane, or when selecting the Values of a Query's Properties specification. This is particularly useful for capturing legacy data not atomized as nominal/ordinal OCHRE properties in the usual way.
    {2017_alphaPicklistI.PNG} Check the picklist option ON
    This strategy also is useful in conjunction with other string-related operators for alphanumeric properties on a Query specification.
    ...
    like "contains" andor "starts with"
    (view changes)
    3:22 pm

More