    {
      "dir": "disk0/00/00/00/22",
      "status_changed": "2009-08-06 19:36:13",
      "pres_type": "paper",
      "userid": 3,
      "full_text_status": "restricted",
      "documents": [
          {
            "eprintid": 22,
            "pos": 1,
            "language": "en",
            "docid": 27,
            "mime_type": "application/pdf",
            "format": "application/pdf",
            "security": "validuser",
            "uri": "https://documents.el-una.org/id/document/27",
            "rev_number": 5,
            "content": "presentation",
            "files": [
                {
                  "uri": "https://documents.el-una.org/id/file/426",
                  "filesize": 1289957,
                  "fileid": 426,
                  "datasetid": "document",
                  "objectid": 27,
                  "filename": "naaug-2005-newberry.pdf",
                  "mtime": "2016-05-27 21:03:06",
                  "mime_type": "application/pdf"
                }
            ],
            "main": "naaug-2005-newberry.pdf",
            "relation": [
              {
                "uri": "/id/document/1626",
                "type": "http://eprints.org/relation/hasVolatileVersion"
              },
              {
                "type": "http://eprints.org/relation/haspreviewThumbnailVersion",
                "uri": "/id/document/1626"
              },
              {
                "type": "http://eprints.org/relation/hasVersion",
                "uri": "/id/document/1626"
              }
            ]
          }
      ],
      "metadata_visibility": "show",
      "keywords": "consortia",
      "refereed": "TRUE",
      "abstract": "This presentation will outline some of the intended and unintended consequences of database architecture choices (one/multiple ADM, one/multiple BIB, etc.). Representatives of three consortia will describe their systems\u2019 architecture and their pros and cons. Areas that will be explored are: functionality, staffing, scalability, and so on. How much do their members share versus keep separate?\r\nVersion: all",
      "type": "conference_item",
      "rev_number": 13,
      "datestamp": "2009-08-06 19:36:13",
      "uri": "https://documents.el-una.org/id/eprint/22",
      "date": "2005-06-07",
      "event_location": "University of Maryland, College Park",
      "corp_creators": [
        "Florida Center for Library Automation"
      ],
      "item_issues_count": 0,
      "event_dates": "June 5-7, 2005",
      "eprint_status": "archive",
      "divisions": [
        "naaug"
      ],
      "event_title": "North American Aleph Users Group Sixth Annual Meeting",
      "title": "Database Architecture for Consortia : How It Effects Your Use of ALEPH -- Sharing, Sort of\r\n",
      "subjects": [
        "aleph"
      ],
      "ispublished": "pub",
      "date_type": "published",
      "creators": [
        {
          "name": {
            "honourific": null,
            "family": "Newberry",
            "lineage": null,
            "given": "Michelle"
          }
        }
      ],
      "eprintid": 22,
      "lastmod": "2016-05-27 21:03:06",
      "event_type": "conference"
    }