Monday, August 20, 2018

AAAC::::DDO Park Archivists - README.first

Revision history: 


All times in these blog "revision histories" are stated in UTC (Universal Coordinated Time/ Temps Universel Coordoné,  a precisification of the old GMT, or "Greenwich Mean Time"), in the ISO-prescribed YYYYMMDDThhmmZ timestamping format. UTC leads Toronto summer civil time by 4 hours and leads Toronto winter time by 5 hours (and lags Stockholm-Helsinki-Tallinn-summer civil time by 3 hours).  


  • 20180822T192200Z/version 1.2.0: Kmo did an update, in essence reporting a favourable incoming e-mail from an officer of the Richmond Hill Public Library. - Kmo reserved the right to make further tiny, nonsubstantive, purely cosmetic, tweaks over the coming 240 hours, as here-undocumented versions 1.2.1, 1.2.2, ... .  
  • 20180822T000700Z (and also earlier)/version 1.1.0: Kmo made some essentially nonsubstantive tweaks, and additionally on the side of substance added references to RASC. - He reserved the right to make further tiny, nonsubstantive, purely cosmetic, tweaks over the coming 240 hours, as here-undocumented versions 1.1.1, 1.1.2, ... .   
  • 20180820T214500Z/version 1.0.0: Kmo uploaded base version.

1. Values Guiding the DDO Park Archivists

  • Through their work on the David Dunlap Observatory and Park (DDO&P) heritage-conservation case, the DDO Park Archivists (the "Archivists") seek to strengthen the causes of cultural-heritage conservation and natural-heritage conservation in Ontario. They see this as their local contribution to a wider project - more necessary than ever, they feel, in these days of social-media manipulation and legislative corruption - namely, the enhancing of civic trust. The wider project is addressed in hundreds of ways by thousands of community volunteers around the world even outside the Archivists' own chosen field, heritage conservation. The Archivists thus note that civic trust is enhanced by high-profile environmentalist organizations, such as the International Tree Foundation, or again by Greenpeace,  and (looking still further afield) by such non-profit private-sector organizations as l'Arche, Médecins sans Frontières, the Free Software Foundation, and Amnesty International. The Archivists note that although their own scope is municipal, their work, if done well, is nevertheless liable to set a beneficial example for civic-spirited individuals and civic-spirited groupings outside Richmond Hill, even outside Canada. 
  • The DDO Park Archivists see their work as part of the truth-and-reconciliation outreach sketched by one of their number, Dr Toomas Karmo (in the 1935-through-2008 staff-documentation formalism used internall at DDO, "Kmo"), in his http://toomaskarmo.blogspot.com posting of 2018-06-10, headed  "The 'DDO&P Conflict', 2007-09-10 to 2018-06-09" (available at http://toomaskarmo.blogspot.com/2018/06/)). Mindful both that truth is foundational to reconciliation and that concealment is an adversary of truth, the Archivists undertake to put into their archiving and public cataloguing queue all the DDO&P Conservation-case materials available to them, without any attempt at filtering and censorship, applying just the following proviso: If it seems to the Archivists that the ethics of privacy protection require some material to be suppressed, then they will flag their act of suppression in their publicly viewable archive cataloguing, stating reasons, and describing their suppressed material in as much detail as the ethics of privacy protection may allow. The Archivists do not envisage that censorship will in fact be needed. They do, however, further undertake to consult with the appropriate government authority or authorities (the Information and Privacy Commissioner of Ontario, the Privacy Commissioner of Canada, ... ) in the (remotely conceivable) contingency of a censorship question arising. The Archivists' core principle is the same as the core principle of the Free Software Foundation: We eschew secrets; our work is an open book, a non-governmental contribution to the public record.  

2. Overview of the DDO Park Archivists Projects


  • The main effort of the Archivists, at least in the short term (2018, 2019, 2020) is the cataloguing and curating of half a dozen crates of papers from DDO&P conservation activist Toomas Karmo (resident in Richmond Hill from 2006 November through 2018 October, but from 2018 November onward to be considered a resident in the dark-sky compound of Tartu Observatory (in the Tõravere hamlet, Nõo Commune, Tartu County, Estonia)).  
  • As time may allow, the Archivists will make some efforts at curating also Toomas Karmo's digital archives (most notably, e-mail inboxes and e-mail outboxes) from the DDO&P conservation case. 
  • The Archivists will consider working with other pertinent actors in the DDO&P conservation case, including the Richmond Hill Naturalists, the DDO Defenders, and the Royal Astronomical Society of Canada (RASC), to curate their papers and digital archives also, in the event that mutual agreements can be reached with them. 
  • The Archivists invite all other public and private entities, including Corsica Developments Inc. and its partners (as creators of a 32-hectare subdivision, comprising a little under 600 units of housing, from the legacy 77 DDO&P greenspace hectares: 77 hectares were in play originally; 32 hectares were lost, 45 hectares are saved), and again the Royal Astronomical Society of Canada (in some past years a party with contractual obligations to Corsica) to donate papers and digital materials to their work.   


3. Relation of the DDO Park Archivists to Municipal and Provincial Authorities


The Archivists are happy to accept any support which may in future be offered them at the municipal and provincial levels. 

They note that their initial efforts at municipal outreach are  now showing some degree of progress.

(A) In the 2018 summer, the Local History Room at the Richmond Hill Public Library Main Branch found itself unable, the low-key courtesy of Dr Karmo's approach notwithstanding, to allow Archivists' cataloguing work to be done at its own worktables, and additionally (the courtesy of Dr Karmo's approach notwithstanding) in 2018 August reserved its decision on whether to accept any eventual - to be sure, as Dr Karmo indicated to the Room, duly processed, duly catalogued -  materials from the Archivists.  But (B) on 2018-08-22, an appropriate authority at the Richmond Hill Public Library queried Dr Karmo by e-mail, in a way that signalled an interest in archiving. 

The Archivists further note (and Dr Karmo indicated this to the Library, in replying to the 2018-08-22 query) that in their own private judgement, the public interest would be best served by a two-pronged archiving solution, in which all their materials become lodged with the Archives of Ontario (as a distinctively secure and distinctively well-equipped Ontario repository), and in which copies of some or all of their materials become lodged with the (duly equipped, and yet less formidably equipped) Local History Room of the Richmond Hill Public Library Main Branch. 

4. Relation of the DDO Park Archivists to Other Non-Governmental Community Organizations

The Archivists are not formally connected with either of the two principally relevant non-governmental community organizations in the 2007-through-2018 conservation casework, namely the Richmond Hill Naturalists and the DDO Defenders. They also are not formally connected with RASC, or with any branch  of government, or with any commercial organization. A caveat: one or more of the Archivists either is now or has in the past been a member of one or more of the following: the Richmond Hill Naturalists; the DDO Defenders; the Royal Astronomical Society of Canada. 

The Archivists find themselves in full philosophical agreement with the Naturalists, concurring with them that the destruction by commercial parties of 32 hectares out of the 77-hectare legacy DDO&P greenspace  injures Ontario's public interest. 

The Archivists invite the DDO Defenders to agree formally, over coming years, with their own philosophical position, and in the happy event of a formal agreement-on-values to consider making the Archivists a branch or unit within their own organization, or in some other way to formalize a cooperation with them.

The Archivists would welcome as associates, engaged in the practical work of sorting and cataloguing, history-interested individuals from within the Naturalists, from within the Defenders, and from within RASC. They would not require such associate individuals to subscribe to the conservationist philosophical principles of the Archivists themselves. 


[This is the end of the current posting.] 

AAAE::::User Guide for the "Finding Aid"

Revision history: 

All times in these blog "revision histories" are stated in UTC (Universal Coordinated Time/ Temps Universel Coordoné,  a precisification of the old GMT, or "Greenwich Mean Time"), in the ISO-prescribed YYYYMMDDThhmmZ timestamping format. UTC leads Toronto summer civil time by 4 hours and leads Toronto winter time by 5 hours (and lags Stockholm-Helsinki-Tallinn-summer civil time by 3 hours).  
  • 20180819T0118000Z/version 1.0.0: Kmo uploaded base version.

0. A Preliminary Inspirational Remark Regarding the DDO&P Hardcopy-Archive Finding Aid

The DDO&P land-conservation case was for much or all of the 2007-through-2018 "Dunlap War" Canada's weightiest heritage-conservation case. It is therefore unsurprising that the case should have generated, from the desk of the present writer (Toomas Karmo) alone, over six crates of paper, now in need of curation, and that the total burden of paper from the private sector (leaving aside the Town's own filing cabinets, and other such things within public-sector working offices) should comprise something on the order of ten or fifteen crates.

Although the curation task may be thought daunting, it may also be thought exhilarating: here we have a problem requiring the sort of attention to detail, and the sort of patience, associated with Scotland Yard and similar agencies of official justice. One recalls how HM Government procured and programmed "HOLMES" ("Home Office Large Major Enquiry System") from the 1980s onward, achieving instant computerized retrieval of operational particulars for any arbitrary person-of-United-Kingdom-interest. Although this achievement has its dark, Orwellian side, it is helpful here to concentrate on HOMES's brighter side - thinking how many crime victims HOLMES must have helped, as the police have again and again used it to get criminals into court.

Additional inspiration may be had, if needed, from an ancient bunker at the Vatican archives, or from a roboticized document-transport monorail at MI5 (at Millbank, near Lambeth Bridge: no, folks, you do not have to infliltrate MI5 to see this marvel of law-and-order: some YouTube footage exists, somewhere). 

Or from the fictional Detective whose name got perpetuated in HM Government's above-mentioned cyber, assisting  Wilhelm Gottsreich Sigismond von Ormstein, Grand Duke of Cassel-Felstein (this particular client was also, we are told, a hereditary King) in the troubling matter of advenuress Irene Adler, as chronicled under "A Scandal in Bohemia":

"Kindly look her up in my index, Doctor," murmured Holmes without opening his eyes. For many years he had adopted a system of docketing all paragraphs concerning men and things, so that it was difficult to name a subject or a person on which he could not at once furnish information. In this case I found her biography sandwiched in between that of a Hebrew rabbi and that of a staff-commander who had written a monograph upon the deep-sea fishes.

"Let  me  see!"  said  Holmes.   "Hum!   Born  in New Jersey in the year 1858. Contralto - hum! La Scala, hum!  Prima donna Imperial Opera of Warsaw - yes! Retired from operatic stage - ha! Living in  London - quite  so!   Your  Majesty,  as  I  understand, became entangled with this young person /.../"

 

 

1. Design Principles of the DDO&P Hardcopy-Archive Finding Aid


  • Visibility: The Finding Aid must be visible to any member of the surfing public. 
  • Security: The Finding Aid must be made as secure as possible against infrastructure accidents (for instance, against Internet collapse or Internet degradation, or again against accidents, such as fire or flood, befalling cyber storage media).
  • Searchability: The Finding Aid must support searches for arbitrary text strings (for example, for the string aluminizing chamber, as the designation of a piece of telescope support equipment, or again for the string 1935, as the designation of a year).
  • Simplicity: The Finding Aid must be organized in a way which is as far as possible self-evident.

2.  How the DDO&P Hardcopy-Archive Finding Aid Seeks Visibility 


It is hoped to make the Finding Aid available to anyone with a Web browser. 

Additionally, it is hoped to make the Finding Aid available in whatever public archive (or archives) eventually stores (or store) the DDO&P hardcopy archive itself.  The Aid should be available in such an archive (or such archives) in two forms - on the one hand as printed paper, and on the other as computer files, stored on some such local archive-curated medium as a DVD disk, or an institutional spinning-platter hard drive, or an institutional solid-state disk drive, or an institutional USB stick.


3. How the DDO&P Hardcopy-Archive Finding Aid Seeks Security


When the Finding Aid is served out as Web content to the general Web-surfing public, the selected server hardware should be as robust as possible. This requires selecting a Web-server solution backed by a large corporation, with multiple data centres around the world and a large engineering crew, and ideally requiring no subscription fees. The blogspot family of servers (ultimately under the jurisdiction of Google, who offer blogspot to everyone, as a free-of-cost blogging solution) satisfies this robustness requirement. Thanks to the geographical reach and technical skill of Google, the blogspot family is perhaps now more robust than any alternative, at any rate within the universe of solutions requiring no subscription fees.


4. How the DDO&P Hardcopy-Archive Finding Aid Seeks Searchability


It is not enough for the Finding Aid to list documents. A Finding Aid in a usable archive has to exceed bare inventory. 

(a) The following example illustrates relevant exceeding-mere-inventory principles. 

On 2009-10-25, the Liberal (Richmond Hill's main community newspaper) published a letter-to-editor mildly remarkable less for what it did than for what it failed to do. The letter mentioned DDO&P and also mentioned the longstanding problem of a museum for Richmond Hill. But the letter was mildly remarkable for its failure to note that the problems are connected. 

A mere inventory would have some bare annotation such as "Liberal, letter to editor 2009-10-25, mentioning DDO&P".  

What is by contrast needed, however, is a description of the letter, going at at any rate so far as to indicate that it mentions the museum, and also indicating who wrote it - in this case, a description incorporating at least the word museum, and the author's name (Ana Nair), and the group affiliation which the author caused to be printed in the newspaper under her surname (in her case, Richmond Hill Museum Support Group). 

Researchers can then search under such strings as museum, Nair, and Museum Support

- It is in fact appropriate to show the full entry herewith (at any rate as drafted by the present writer, Toomas Karmo, in the late summer of 2018), and to add supplementary explanations:

* UTC=20091025T000001Z~
  __The Liberal print edition, 2009-10-25,
    lttr-to-editor headed "Town needs museum,
    not another office", from
    ((QUOTE))
      Ana Nair
      Richmond Hill Museum Support Group
    ((/QUOTE)) 
    __mentions DDO&P and mentions museum problem
      __but does not connect this pair of dots

(Supplementary explanations: 

(1) The UTC timestamp reflects the fact that the Liberal went to press in the evening of 2009-10-24, being formally asserted by its publisher to be the edition of 2009-10-25. It is a reasonable guess that layout was finished, and the press run started, just a little after UTC=20091024T235959Z (in other words, just a little after 2009-10-24 19:59:59 EDT; UTC leads EDT by 4 hours, and leads EST by 5 hours; it is EDT which governs Ontario until the end of October, when the local civil clocks get "put back one hour"). The "~" in the timestamp is a flag that this UTC timestamp is a guess. Where a guess regarding the UTC year-month-day-hour-minute-second timestamp is made under conditions of significantly greater uncertainty (this is especially likely with DDO&P conservation-relevant papers from the years and decades prior to 2008) a flag like "~~", or in an extreme case even "~~~~", would be required.

(2) Enough description is given to alert the researcher to a relevant negative fact, namely, that this letter does not shed much DDO&P-relevant light on the Town's longstanding museum problem. A researcher will thereby be spared the effort of retrieving a document that in the final analysis does have to be conserved, and yet does not in the final analysis say very much.)

(b) Here is a second example illustrating relevant principles. 

In the Richmond Hill Town Council meeting of 2013-09-23 (in UTC terms, "20130923T233000Z"; the meeting was nominally called to order at 19:30:00 EDT, i.e., at 23:30:00 UTC), a town resident recalled for Mayor and Council the council meeting of 2013-06-24, in which the Town Solicitor had first given one answer, then upon probing from the public podium reversed himself and given a contrary answer, to a question regarding the nature of legal title to the DDO&P "Panhandle" land parcel. (He had first claimed title to be "Absolute", and then later, under probing from the podium, admitted what the podium speaker was able to demonstrate with a photocopy of Land Registry documentation, namely that the title was "Conversion Qualified". This resident put a photocopy of a relevant 2013-06-24 document onto the 2013-09-23 camera table, for Mayor and Council to inspect via the video monitors as the resident explained the case.

A mere inventory would have some bare annotation such as "papers pertaining to Town Council meeting of 2013-09-23". 

What is needed, however, is a description of the papers - in this case, something like  photocopy of sheet used at video-camera table 2013-06-24, showing "yes" crossed out, "no" circled, as Town Solicitor reversed himself re nature of title to DDO Panhandle lands

A researcher should be able to find this description with some text searches, for instance under the string camera table, and again under the string Town Solicitor, and again under the string Panhandle

Since this particular paper, unlike many in the archive, is important (it not only touches on an intrinsically important Council Chamber event, but additionally may be "rare" or "unique", in the sense of being unavailable in such other collections as the Town Council meeting minutes, or the Public-Library-curated Liberal print-edition microfiche), its importance should be flagged, with some such flag as  IMPORTANCE_RANKING=90outof100.  A researcher should be able to retrieve, through some simple text search, all the Finding Aid entries which are importance-flagged (and can then, if necessary, plod manually through all the importance-flagged entries, if for some reason not aware of the advisability of starting in this case with such concrete search strings as camera table, Town Solicitor, and Panhandle).  

For the casual researcher working with the Finding Aid on the Web, it might suffice to Google within the blogspot server, using not such a Google string as Panhandle (that query would try to pull up everything on the normal public Web, on any normal public server at all, referring in any way at all to the handle of a pan) but such a Google string as Panhandle site:ddoparkarchivists.blogspot.com. (It is a key, although perhaps not a well-known, feature of Google that  "roohar goozar wootar site:foobar.com" restricts searches for the string "roohar goozar wootar" to the particular server foobar.com.)

Less causal researchers, possessing sleuth-grade computer equipment (this need not nowadays mean "supercomputer", but does nowadays pretty inevitably mean "some flavour (e.g., Linux) of Unix)" can (1) procure the actual computer files comprising the Filing Aid - for instance, by downloading them over the Internet from the blogspot server -  and (2) analyze their procurement with appropriate sleuth-grade tools, to get at least some of the effect of Boolean queries in a formal SQL database. (In particular, the Linux /bin/grep tool, combined with Unix "pipes" in a typical Unix shell environment such as /bin/bash, can secure the effect of Boolean AND, as when one seeks the Finding Aid entries that both refer to the Panhandle and are flagged as important.)







5. How the DDO&P Hardcopy-Archive Finding Aid Seeks Simplicity 


Formal databases (in contemporary computer technology, erected on a a foundation of the SQL query language, and implemented as binary files) have their place in information management. In the case of DDO&P, a formal database would be overkill. Databases require trained personnel for their maintenance. Further, binary files are specially vulnerable to corruption, as when a hard drive begins to fail. The relevant rule of thumb is consequently the following: Use SQL where the number of records is in the high hundreds of thousands, or worse (as in airline work, in police work, or in large-scale manufacturing). Where the number of records is in the high or low tens of thousands (or still lower), use instead human-readable text files, searching them with the conventional (and rather powerful) Unix text-search tools.  

Human-readable text files are sometimes in contemporary computer technology implemented as *.docx files or *.pdf files, being in such cases created with "word processor" software (such as LibreOffice, OpenOffice, or Microsoft Office). 

However, *.docx files and *.pdf files, and other format-intensive human-readable file formats, are less easily searched by machine (optimally, running some flavour of Unix) than *.txt  ("plain text", "flat ASCII") files.

Further, "word processor" software raises compatibility problems over a long timeframe. In particular, MS Word formats have been changing as the decades pass. The Government of Canada around the year 2000 was supporting the Canadian software corporation Corel by requiring WordPerfect formatting. But WordPerfect has now, as of 2018, essentially disappeared from the market. Might some similar misfortune overtake MS Word by 2030 or so? Or, if Microsoft survives to 2030, might it not by that point have radically altered its file-saving formats, to a point at which 2018-era MS Word documents become unreadable outside the walls of highly specialized institutions?

Flat ASCII, by contrast, was in widespread use as early as the 1970s and shows no signs of disappearing from the evolving information-technology world. Its position is rendered rather secure by the fact that the world's underlying computing infrastructure - the source code for programs in C, for example, and the source code for HTML Web pages - gets authored in flat ASCII. 

The preferred solution for the Finding Aid therefore involves (A) storing files as mere flat ASCII on whatever public-archive storage media may be used (for instance, at least in the 2018 era, DVD media, or else USB sticks), and (B) creating them also as mere flat ASCII on whatever computers the Finding Aid creator(s) themselves may be using as they update and maintain the Filing Aid - Linux workstations? Apple laptops? Microsoft laptops? Android (in essence, a user-friendly Linux derivative) mobiles? Android tablets? 

With working Finding Aid files created and maintained in flat ASCII, it is trivial to upload their various successive versions to public blogspot servers, or to other public servers, and also trivial to take hardcopy printout.


[This is the end of the current posting.]

AAAN::::Sorting-Codes List for the "Finding Aid"

* period from_earlies_times thru end 1932:  OLA*  
  + OLAA::::"Finding Aid" - prehistory to 17991231T235959Z [EMPTY] 
  + OLAB::::"Finding Aid" - 18000101T000000Z to 18991231T595959Z [EMPTY]
  + OLAC::::"Finding Aid" - 19000101T000000Z to 19091231T235959Z [EMPTY]
  + OLAD::::"Finding Aid" - 19100101T000000Z to 19101231T235959Z [EMPTY]
  + OLAE::::"Finding Aid" - 19110101T000000Z to 19111231T235959Z [EMPTY]
  + OLAF::::"Finding Aid" - 19120101T000000Z to 19121231T235959Z [EMPTY]
  + OLAG::::"Finding Aid" - 19130101T000000Z to 19131231T235959Z [EMPTY]
  + OLAH::::"Finding Aid" - 19140101T000000Z to 19141231T235959Z [EMPTY]
  + OLAI::::"Finding Aid" - 19150101T000000Z to 19151231T235959Z [EMPTY]
  + OLAJ::::"Finding Aid" - 19160101T000000Z to 19161231T235959Z [EMPTY]
  + OLAK::::"Finding Aid" - 19170101T000000Z to 19171231T235959Z [EMPTY]
  + OLAL::::"Finding Aid" - 19180101T000000Z to 19181231T235959Z [EMPTY]
  + OLAM::::"Finding Aid" - 19190101T000000Z to 19191231T235959Z [EMPTY]
  + OLAN::::"Finding Aid" - 19200101T000000Z to 19201231T235959Z [EMPTY]
  + OLAO::::"Finding Aid" - 19210101T000000Z to 19211231T235959Z [EMPTY]
  + OLAP::::"Finding Aid" - 19220101T000000Z to 19221231T235959Z [EMPTY]
  + OLAQ::::"Finding Aid" - 19230101T000000Z to 19231231T235959Z [EMPTY]
  + OLAR::::"Finding Aid" - 19240101T000000Z to 19241231T235959Z [EMPTY]
  + OLAS::::"Finding Aid" - 19250101T000000Z to 19251231T235959Z [EMPTY]
  + OLAT::::"Finding Aid" - 19260101T000000Z to 19261231T235959Z [EMPTY]
  + OLAU::::"Finding Aid" - 19270101T000000Z to 19271231T235959Z [EMPTY]
  + OLAV::::"Finding Aid" - 19280101T000000Z to 19281231T235959Z [EMPTY]
  + OLAW::::"Finding Aid" - 19290101T000000Z to 19291231T235959Z [EMPTY]
  + OLAX::::"Finding Aid" - 19300101T000000Z to 19301231T235959Z [EMPTY]
  + OLAY::::"Finding Aid" - 19310101T000000Z to 19311231T235959Z [EMPTY]
  + OLAZ::::"Finding Aid" - 19320101T000000Z to 19321231T235959Z [EMPTY]
* partdecade 1933 thru end 1935: OLB*
  __divide this up into 12 quarter-years 
    (_A,B,C,D,E,F,G,H,I,J,K,L)
* partdecade 1936 thru end 1939: OLC*
  __divide this up into 16 quarter-years 
    (_A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P)
* decade 1940 thru end 1949:     OLD*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* decade 1950 thru end 1959:     OLE*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* decade 1960 thru end 1969:     OLF*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* decade 1970 thru end 1979:     OLG*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* decade 1980 thru end 1989:     OLH*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* decade 1990 thru end 1999:     OLI*
  __divide this up into 20 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N,O.P,Q,R,S,T)
* partdecade 2000 thru end 2006: OLJ*
  __divide this up into 14 half-years
    (_A,B,C,D,E,F,G,H,I,J,K,L,M.N)
    __JA: from 20000101T000000Z to 20000630T235959Z [EMPTY]
    __JB: from 20000701T000000Z to 20001231T235959Z [EMPTY]
    __JC: from 20010101T000000Z to 20010630T235959Z [EMPTY]
    __JD: from 20010701T000000Z to 20011231T235959Z [EMPTY]
    __JE: from 20020101T000000Z to 20020630T235959Z [EMPTY]
    __JF: from 20020701T000000Z to 20021231T235959Z [EMPTY]
    __JG: from 20030101T000000Z to 20030630T235959Z [EMPTY]
    __JH: from 20030701T000000Z to 20031231T235959Z [EMPTY]
    __JI: from 20040101T000000Z to 20040630T235959Z [EMPTY]
    __JJ: from 20040701T000000Z to 20041231T235959Z [EMPTY]
    __JK: from 20050101T000000Z to 20050630T235959Z [EMPTY]
    __JL: from 20050701T000000Z to 20051231T235959Z [EMPTY]
    __JM: from 20060101T000000Z to 20060630T235959Z [EMPTY]
    __JN: from 20060701T000000Z to 20061231T235959Z [NONEMPTY]

* year 2007: OLK*
  __divide this up into 4 quarter-years (A,B.C.D)
    __KC: from 20070701T000000Z to 20070930T235959Z [EMPTY]
    __KD: from 20071001T000000Z to 20071231T235959Z [EMPTY]
* year 2008: OLL*
  __divide this up into 4 quarter-years (A,B,C,D)
    __LA: from 20080101T000000Z to 20080331T235959Z [NONEMPTY]
      __DONE
    __LB: from 20080401T000000Z to 20080630T235959Z [EMPTY]
      __DONE
    __LC: from 20080701T000000Z to 20080930T235959Z [NONEMPTY]
      __DONE
    __LD: from 20081001T000000Z to 20081231T235959Z [NONEMPTY]
      __DONE
* year 2009: OLM*
  __divide this up into 4 quarter-years (A,B,C,D)
    __MA: from 20090101T000000Z to 20090331T235959Z [NONEMPTY]
      __DONE
    __MB: from 20090401T000000Z to 20090630T235959Z [NONEMPTY]
      __DONE
    __MC: from 20090701T000000Z to 20090930T235959Z [NONEMPTY]
      __DONE
    __MD: from 20091001T000000Z to 20091231T235959Z [NONEMPTY]
      __DONE@20180808T135410Z
* year 2010: OLN*
  __divide this up into 4 quarter-years (A,B,C,D)
    __NA: from 20100101T000000Z to 20100331T235959Z [NONEMPTY]
      __DONE@20180808T135553Z
    __NB: from 20100401T000000Z to 20100630T235959Z [NONEMPTY]
      __DONE@20180808T135723Z
    __NC: from 20100701T000000Z to 20100930T235959Z [NONEMPTY]
      __DONE@20180808T135834Z
    __ND: from 20101001T000000Z to 20101231T235959Z [NONEMPTY]
      __DONE@20180808T140038Z
* year 2011: OLO*
  __divide this up into 4 quarter-years (A,B,C,D)
    __OA: from 20110101T000000Z to 20110331T235959Z [EMPTY]
      __DONE@20180808T140211Z
    __OB: from 20110401T000000Z to 20110630T235959Z [NONEMPTY]
      __DONE@20180808T140316Z
    __OC: from 20110701T000000Z to 20110930T235959Z [EMPTY]
      __DONE@20180808T140418Z
    __OD: from 20111001T000000Z to 20111231T235959Z [EMPTY]
      __DONE@20180808T140418Z
* year 2012: OLP*
  __divide this up into 4 quarter-years (A,B,C,D)
    __PA: from 20120101T000000Z to 20120331T235959Z [NONEMPTY]
      __DONE@20180808T140631Z
    __PB: from 20120401T000000Z to 20120630T235959Z [NONEMPTY]
      __DONE@20180808T140814Z
    __PC: from 20120701T000000Z to 20120930T235959Z [NONEMPTY]
      __DONE@20180808T141014Z
    __PD: from 20121001T000000Z to 20121231T235959Z [NONEMPTY]
      __DONE@20180808T141116Z
* year 2013: OLQ*
  __divide this up into 4 quarter-years (A,B,C,D)
    __QA: from 20130101T000000Z to 20130331T235959Z [NONEMPTY]
      __DONE@20180808T141313Z
    __QB: from 20130401T000000Z to 20130630T235959Z [NONEMPTY]
      __DONE@20180808T141441Z
    __QC: from 20130701T000000Z to 20130930T235959Z [NONEMPTY]
      __DONE@20180808T141556Z
    __QD: from 20131001T000000Z to 20131231T235959Z [NONEMPTY]
      __DONE@20180808T141658Z
* year 2014: OLR*
  __divide this up into 4 quarter-years (A,B,C,D)
    __RA: from 20140101T000000Z to 20140331T235959Z [EMPTY]
      __DONE@20180808T141932Z
    __RB: from 20140401T000000Z to 20140630T235959Z [EMPTY]
      __DONE@20180808T141932Z
    __RC: from 20140701T000000Z to 20140930T235959Z [EMPTY]
      __DONE@20180808T141932Z
    __RD: from 20141001T000000Z to 20141231T235959Z [NONEMPTY]
      __DONE@20180808T142038Z
* year 2015: OLS*
  __divide this up into 4 quarter-years (A,B,C,D)
    __SA: from 20150101T000000Z to 20150331T235959Z [EMPTY]
      __DONE@20180808T142241Z
    __SB: from 20150401T000000Z to 20150630T235959Z [NONEMPTY]
      __DONE@20180808T142354Z
    __SC: from 20150701T000000Z to 20150930T235959Z [EMPTY]
      __DONE@20180808T142420Z
    __SD: from 20151001T000000Z to 20151231T235959Z [NONEMPTY]
      __DONE@20180808T142505Z
* year 2016: OLT*
  __divide this up into 4 quarter-years (A,B,C,D)
    __TA: from 20160101T000000Z to 20160331T235959Z [NONEMPTY]
      __DONE@20180808T142716Z
    __TB: from 20160401T000000Z to 20160630T235959Z [EMPTY]
      __DONE@20180808T142755Z
    __TC: from 20160701T000000Z to 20160930T235959Z [NONEMPTY]
      __DONE@20180808T142846Z
    __TD: from 20161001T000000Z to 20161231T235959Z [NONEMPTY]
      __DONE@20180808T142951Z
* year 2017: OLU*
  __divide this up into 4 quarter-years (A,B,C,D)
    __UA: from 20170101T000000Z to 20170331T235959Z [NONEMPTY]
      __DONE@20180808T144712Z
    __UB: from 20170401T000000Z to 20170630T235959Z [EMPTY]
      __DONE@20180808T144712Z
    __UC: from 20170701T000000Z to 20170930T235959Z [EMPTY]
      __DONE@20180808T144935Z
    __UD: from 20171001T000000Z to 20171231T235959Z [EMPTY]
      __DONE@20180808T144935Z
* year 2018: OLV*
  __divide this up into 4 quarter-years (A,B,C,D)
    __VA: from 20180101T000000Z to 20180331T235959Z [EMPTY]
      __DONE@20180808T145155Z
    __VB: from 20180401T000000Z to 20180630T235959Z [EMPTY]
      __DONE@20180808T145155Z
    __VC: from 20180701T000000Z to 20180930T235959Z [EMPTY]
      __DONE@20180808T145155Z
    __VD: from 20181001T000000Z to 20181231T235959Z [EMPTY]
      __DONE@20180808T145155Z
* year 2019: OLW*
  __divide this up into 4 quarter-years (A,B,C,D)
* year 2020: OLX*
  __divide this up into 4 quarter-years (A,B,C,D)
* year 2021: OLY*
  __divide this up into 4 quarter-years (A,B,C,D)
* year 2022: OLZ*
  __divide this up into 4 quarter-years (A,B,C,D)

AAAC::::DDO Park Archivists - README.first

Revision history:  All times in these blog "revision histories" are stated in UTC (Universal Coordinated Time/ Temps Universel...