    {
      "eprint_status": "archive",
      "title": "Scripting Primo Enrichments",
      "userid": 23,
      "date": "2011-05",
      "divisions": [
        "eluna_conf"
      ],
      "datestamp": "2011-05-31 16:50:10",
      "event_type": "conference",
      "pres_type": "lecture",
      "subjects": [
        "primo"
      ],
      "event_title": "ELUNA 2011",
      "eprintid": 680,
      "metadata_visibility": "show",
      "documents": [
          {
            "docid": 872,
            "format": "application/vnd.ms-powerpoint",
            "main": "Scripting_Primo_Enrichments-Celik.pptx",
            "uri": "https://beta-documents.el-una.org/id/document/872",
            "mime_type": "application/vnd.ms-powerpoint",
            "files": [
                {
                  "objectid": 872,
                  "mtime": "2016-05-27 21:05:25",
                  "datasetid": "document",
                  "uri": "https://beta-documents.el-una.org/id/file/12253",
                  "mime_type": "application/vnd.ms-powerpoint",
                  "fileid": 12253,
                  "filename": "Scripting_Primo_Enrichments-Celik.pptx",
                  "filesize": 4786713
                }
            ],
            "language": "en",
            "security": "validuser",
            "rev_number": 3,
            "pos": 1,
            "eprintid": 680,
            "content": "presentation"
          }
      ],
      "event_dates": "11-13 May 2011",
      "event_location": "Milwaukee, Wisconsin",
      "refereed": "FALSE",
      "type": "conference_item",
      "abstract": "Writing enrichment plug-ins for Primo can be difficult. For starters you need to know Java and you need a good understanding of the inner workings of Primo. Thanks to the Java Scripting API we wrote an enrichment plug-into call external scripts written in Ruby or any JSR-223 compliant scripting language. With this newly found power we started creating enrichments to add relations (UP-, DOWN- and PAR-links), author authorities.... Everything was working great on our test environment but we hit a huge performance wall on production. It would take 45 days to enrich 4.6 million records. This was unacceptable. Come and see how we reduced this to 1.5 days.",
      "ispublished": "pub",
      "uri": "https://beta-documents.el-una.org/id/eprint/680",
      "rev_number": 11,
      "full_text_status": "restricted",
      "dir": "disk0/00/00/06/80",
      "lastmod": "2016-05-27 21:05:25",
      "creators": [
        {
          "name": {
            "lineage": null,
            "given": "Mehmet",
            "honourific": null,
            "family": "Celik"
          }
        }
      ],
      "item_issues_count": 0,
      "status_changed": "2011-05-31 16:50:10"
    }