Back to top: Files
Universal codes
An underscore trait in front of a file indicates that the file will not be processed by a program, see for instance:
_files ZJ720.md
| a single underscore indicates that an earlier version of the file from which this page is generated is not to be processed, but is retained in the main subfolder for consultation
|
__ files ZJ715.md
| a double underscore indicates that an earlier version of the file from which this page is generated is retained as a backup for future reference, and is to be filed in a separate subfolder named "INACTIVE."
|
Back to top: Files
File labels for folders of type 1
There is no restriction as to the format of the label for files in folders of type 1.
The only restriction is that extensions .J and .MD, are required for files to be processed respectively by the programs JD and MID.
Back to top: Files
Files with extension .J for JD program
It is suggested that the labels for .J files include simply the date (in the Mozan format) and the initials of the person who wrote the file, with or without a space between the two. It is also possible to add a few words about the content.
Here are two examples of labels:
- J05/I/J/S721 JW.J
- A12/I/J/ZI910mKB seal impressions.J
folder
| date
| initials
| content
| extension
J05/I/J/
| S721 (= July 21, 2008)
| JW (= James L. Walker)
|
| J
|
A12/I/J/
| ZI910 (= September 19, 2024)
| mKB (= Marilyn Kelly-Buccellati)
| seal impressions
| J
| |
Back to top: Files
Files widh extension .MD for MID program
Folders and full labels:
- A20/I/PAGES/A1/Overview.md
- GRM/I/PAGES/A2/05.Categorization principles.md
- MZS/I/PAGES/C2/surface_finds.md
folder
| label
| extension
A20/I/PAGES/A1/
| Overview
| MD
|
GRM/I/PAGES/A2
| 05.Categorization principles
| MD
|
MZS/I/PAGES/C2/
| surface_finds
| MD
| |
Back to top: Files
File labels for folders of type 2 (V/W)
Each label follows a strictly delimited format. It consists of six fields, of which the first four are required (highlighted here in grey), while hte first five do not allow spaces. See the following examples:
- V23d2016 J2q566.2 U816 dM fg f220.jpg
- V19d3001 J3v10 P801 dM.JPG
- V16d7017 MCVv1 N711 jjj Zcs-an fox hole.JPG
- V18d8013 MCVv4 P818 dM Zcs-mt localized shelter from above.JPG
- V23Fp0101 MPRv200 ZA614 xxx -vs visiting students from Hassaka.jpg
- W23Nc1503 A10q0249.1 xxxx mTS si cylinder seal partial bird table.JPG
- W23Od0118 A01.221 xxxx cJH si f729.JPG
| 1 referent
| 2 element
| 3 date
| 4 initials
| 5 definition
| 6 notes
1
| V23d2016
| J2q566.2
| U816
| dM
| fg
| f220
|
2
| V19d3001
| J3v10
| P801
| dM
|
|
|
3
| V16d7017
| MCVv1
| N711
| jJJ
| Zcs6-an
| fox hole
|
4
| V18d8013
| MCVv4
| P818
| dM
| Zcs-mt
| localized shelter from above
|
5
| V23Fp0101
| MPRv200
| ZA614
| xxx
| -vs
| visiting students from Hassaka
|
6
| W23Nc1503
| A10q0249.1
| xxxx
| mTS
| si
| cylinder seal partial bird table
|
7
| W23Od0118
| A01.221
| xxxx
| cJH
| si
| f729
| |
Back to top: Files
Field 1: referent
This field consists of the subfolder label (e. g., V23d20) followed by a sequential number of the photo or drawing (e.g., 16).
Back to top: Files
Field 2: element
This field gives the label of the element in question.
Back to top: Files
Field 3: date
This field gives the date in the standard Mozan format.
If a date is unknown, one uses xxxx.
Back to top: Files
Field 4: initials
This field gives the initials of the file author in hte standard Mozan format.
If the author is unknown, one uses xxx.
Back to top: Files
Field 5: definition
This field gives the definition of the element in question, according to the list given in the main lexicon.
In practice, this field is used especially for movable items, since, for stationary items (as in example 2), a “view” typically includes several features and also items. It is primarily with conservation and site presentation images that the fifth field is used, as in examples 3-4.
Back to top: Files
Field 6: notes
This field is in free format, and allows spaces
The file labels of the VW folders have a strict format because they are processed as such by the VWX program.
V15d7511
| ‑zc_test_on_mortar_just_made
| M922
| sb
|
| xxx
| M922
| sb
| Zco
|
V15d7501
| A12.149
| M914
| sb
|
|
| A12.149
| M914
| sb
| Zco
|
V16d7001
| -zc_north_lip
| N709
| jlw
|
| MCVv1
| N709
| jlw
| Zcs1:df
| north_lip
|
V16d7017
| -zc_foxhole
| N711
| jjj
|
|
| MCVv2
| N711
| jjj
| Zcs6:an
| foxhole
|
V17d9001
| -ZC
| O821
| gb
|
| MCVv3
| O821
| gb
| Zcs4:wf
|
V18d8003
| -preservation
| P818
| dM
| mt
| palace system from above
|
| MCVv4
| P818
| dM
| Zcs2:sc
| scaffolding under construction
|
V19i3901
| -zcw
| Q928
| BML
| wall stabilization
|
| MCVv5
| Q928
| BML
| Zcs1:st
| wall stabilization
|
V19i0101
[under illegal folders]
| Xmd
| Qx03
| bML
| wahal in joints J2
|
|
| MCVv6
| Qx03
| bML
| Zcs1:md
| wahal in joints J2
|
V21x9201
| -x
| S719
| cL
| x general
|
| MCVv6
| S719
| cL
| Zcs
|
V22x1001
| Z11v16
| T726
| gW
| X1
|
| MCVv
| T726
| gW
| Zcs
|
V23x0103
| -zc
| Ux06
| aMH
| zc
|
| MCVv
| Ux06
| zc
| Zcs
|
Back to top: Files
Correlations
|
|
000203 |
within lot |
A1q2-b3.1 |
|
A1 \ O \ QB \ 00020301 |
individual bone within bone group |
A1q2-i |
|
A1 \ O \ QI \ 0002 |
item lot (may include pebbles, beads, wheel) |
(A1q2-i3) |
A1q2.3 |
A1 \ O \ QI \ 000203 |
identified item lot (e.g., a bead lot) |
(A1q2-i3.4) |
A1q2.3.4 |
A1 \ O \ QI \ 00020304 |
individual |
A1q2-p |
|
A1 \ O \ QP \ 0002 |
pottery lot |
A1q2-p3 |
A1q2.3.4 |
|
color medium format |
A1q2-p3.4 |
|
A1 \ O \ QP \ 00020304 |
individual sherd within a sherd group |
Back to top: Files
-------------
Back to top: Files
Labels for ZC referents
Directories:
r | room (Z11rA1) |
v | view (V11x) |
w | wall |
For conservation photos:
V15x01 | monitoring of individual walls |
V15x49 | |
Back to top: Files
Part Two. Analysis-Section A. Constituents
V15x50 | activities |
V15x60 | coverings and floors |
V15x70 | monitoring mechanisms |
V15x80 | deterioration |
V15x90 | post-excavation history |
V21x0201 X05v49 S720 cL 2008 B1north.JPG | [old X format] |
V22x0201 Z11v49 S720 cL Z11rB1-north.JPG | by room |
V21x0316 Z11v68 S721 cL Z11rC1-east.JPG | [old format, view number out of sequence, Z11rC1 allows sorting by room] |
Back to top: Files
Special books
Special books My16:
V13a | archive |
V13d | digital |
V99 | replaces VG for general |
W13w W13a W13p W13b W13t | drawings (or) pencil (or) preliminary (or) traced (or) traced, inked |
X13p | plates |
X13t | thumbnails moved to VW13 |
Back to top: Files
Constituent label and archive structure
[TEXT MISSING, ZGy20 mDP]
Back to top: Files
Summary
Fig. 13-3: Directory structure for individual Units (O320 based on Mx04).
Note: Italics (on white background) refer to categories not present in digital archive.
Back to top: Files
Incidentals
As indicated, incidentals approximate the status of constituents, even though they are structurally quite distinct. One major difference is that there is no sequential numbering of incidentals. Accordingly there is, properly speaking, no real label for incidentals, even if one may use “A1-sg” to refer to a discussion about strategy within A1. In point of fact, such a form of labeling is used within the archive, where observations about overall strategy will be found, sorted chronologically, within a directory \MZ\A\O-\SG.
The codes used to denote incidentals belong, as I have stressed (see section 2.2) to an open system, and are listed lexically in section 7.5.4.
Back to top: Files

Fig. 12-1: Constituents Labels.

Fig. 12-2: Archive Structure.

Fig. 12-3: Subdivision between ranks 1 and 2.
Back to top: Files