BEEED prototype site data export options
: Illya Nokhrin
Minutes: 360
Added some data export options to the BEEED prototype site at BGH’s request. Currently, the export options are:
- pers1.xml (authors prosopography)
- pers2.xml (editors prosopography)
- orgs1.xml (publishers orgography)
- works1.xml (workogragpy)
I also created nodes/edges CSV exports, which are included in the build. I don’t have a ton of experience generating nodes and edges, so I’ve asked BGH to take a look and see if there are things he wants adjusted there I’ve also added a ’Download XML’ option for each browse and results page. The styling for this is currently super basic and will have to be improved later. On a more complex note, I’ve also added a download option for each search result. This hooks into staticSearch’s global Sch object and inserts a ’Download XML’ button above the staticSearch results are (#ssResults). When a search finishes, the new script reads Sch.resultSet and Sch.resultSet.mapDocs to collect document URIs. It then extracts the record IDs and fetches the corresponding XML files from ../data/records/. It also expands authority references by loading works1.xml, pros1.xml, pros2.xml, orgs1.xml, replaces corresp/ref nodes with full authority entries, strips comments, then serializes into a single listBibl element. Finally it downloads the concatenated TEI as beeed-search-results[-query].xml.
This does require some processing to be done on the user’s computer, but, unless our ography files substantially balloon in size (going to 10MB+ per file), I expect we shouldn’t run into any serious slowdown. If that does happen, I can look into implementing lazy loading or JSON-based solutions for the lookup. But I’m not expecting that to be a significant issue.