glam-datasets

file_description ✖

• #SA History Hub GEOJSON Endpoint http://data.history.sa.gov.au/sahistoryhub/{type} Replace {type} with any of the following types to obtain the current geojson for places, things or organisations stored on the SA History Hub website (http://sahistoryhub.com.au): * place * thing * organisation * event 4
• - 1
• #Passengers in History API Documentation# The Passengers in History data endpoint has been provided using an Apache Solr index (see https://lucene.apache.org/solr/) that uses a Drupal Solr 4.x schema (see https://www.drupal.org/project/search_api_solr). See [https://wiki.apache.org/solr/QueryParametersIndex](https://wiki.apache.org/solr/QueryParametersIndex) for more detail surrounding the query syntax. <br /> An example of a basic implementation can be viewed at https://data.history.sa.gov.au/gallery_pih.php?type=vessel&startindex=0 <br /> Replace the type parameter with any of the types listed below to return associated images eg. https://data.history.sa.gov.au/gallery_pih.php?type=passenger&startindex=0 <br /> The example code can be downloaded from https://data.history.sa.gov.au/gallery_pih.php.txt <br /> The open_data index contains 7 different types of content: <br /> * voyage * passenger * vessel * master * port * source * organisation <br/> Additionally, the photo index (photo_index) can be used to retrieve photos (specify the index using the index_id query parameter). <br/> A voyage is centric to most other content types contains references to passengers, vessels and ports. A join query should be used to get information about related content (see https://wiki.apache.org/solr/Join for information surrounding the query syntax for joins). The is_nid field is the unique identifier. <br/> The number of rows per query is limited to 999 so the start and rows query parameters would need to be used to iterate over the entire result set. <br/> There are many response formats available (see https://cwiki.apache.org/confluence/display/solr/Response+Writers). Just add the parameter 'wt' to the query and select the response format eg. json or csv. The default is xml. ##Examples## A typical workflow might be: <br/> Get the voyage/s that arrived in 1836: <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data AND is_field_voyage_year:1836](https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data AND is_field_voyage_year:1836) <br/><br/> Use a join to get the passengers for one of the voyages (use the voyage is_nid field) <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?start=0&rows=50&q={!join from=im_field_passengers to=is_nid}index_id:open_data AND is_nid:944632](https://data.history.sa.gov.au:8983/solr/passengers/select?start=0&rows=50&q={!join from=im_field_passengers%20to=is_nid}index_id:open_data AND is_nid:944632) <br/><br/> Use a join to find the origin and destination of a particular voyage: <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_origin to=is_nid}index_id:open_data AND is_nid:944632](https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_origin to=is_nid}index_id:open_data AND is_nid:944632) <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_destination to=is_nid}index_id:open_data AND is_nid:944632](https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_destination to=is_nid}index_id:open_data AND is_nid:944632) <br/><br/> Use a join to find the vessel for the voyage: <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_vessel to=is_nid}index_id:open_data AND is_nid:944632](https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_vessel to=is_nid}index_id:open_data AND is_nid:944632) <br/><br/> Use a join to find photos of the vessel (using the vessel is_nid): <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:photo_index AND im_file_usage_list:920026](https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:photo_index AND im_file_usage_list:920026) <br/><br/> Use a join to find out where a vessel was built (using the vessel is_nid): <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_built_where to=is_nid}index_id:open_data AND is_nid:923958](https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_built_where to=is_nid}index_id:open_data AND is_nid:923958) <br/><br/> Use a join to find the built by organisation for a particular vessel: <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_field_built_by to=is_nid}index_id:open_data AND is_nid:923958](https://data.history.sa.gov.au:8983/solr/passengers/select?q={!join%20from=is_field_built_by%20to=is_nid}index_id:open_data%20AND%20is_nid:923958) <br/><br/> Get organisation details (using the organisation is_nid): <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data AND ss_type:organisation AND is_nid:916199](https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data%20AND%20ss_type:organisation%20AND%20is_nid:916199) <br/><br/> Or find all vessels built by the organisation (using the organisation is_nid): <br/> [https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data AND is_field_built_by:916199](https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data%20AND%20is_field_built_by:916199) <br/><br/> ##Other Useful Queries Find all photos that are attached to a passenger: <br/> data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=is_nid to=im_file_usage_list}ss_type:(passenger OR image) <br/><br/> Or find all passengers that have a photo attached (the reverse): <br/> data.history.sa.gov.au:8983/solr/passengers/select?q={!join from=im_file_usage_list to=is_nid}ss_type:(passenger OR image) <br/><br/> All fields are searchable (see listing below). There are many search options using the Apache Solr query syntax. For instance to find all vessels that have the word ‘Adelaide’ in their tm_title field but not the word ‘port’: <br/> data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data AND ss_type:vessel AND tm_title:(adelaide -port) <br/> In this case ss_type is specifically set to be ‘vessel’. The – represents negation of the term. There are many more options – refer to a good blog here [https://yonik.com/solr/query-syntax/](https://yonik.com/solr/query-syntax/) <br/><br/> Facet search on the voyage destination for a date range between 1834 and 1836: <br/> https://data.history.sa.gov.au:8983/solr/passengers/select?rows=0&q={!join%20from=is_nid%20to=is_field_destination}index_id:open_data&fq=ds_field_depart_date:[1834-01-01T00:00:00Z%20TO%201836-12-31T12:59:59Z]&facet=on&facet.field=is_field_destination <br/> In this case use a port search by node to get the titles of the ports eg.(using the first facet): <br/> https://data.history.sa.gov.au:8983/solr/passengers/select?q=index_id:open_data%20AND%20is_nid:887339 <br/> The answer is most likely to be Sydney! <br/><br/> ##Content Type Fields## ###Passenger <br/> * is_nid * ss_type * tm_field_occupation * tm_field_surname * tm_field_firstname * is_field_age * is_arrival_year <br/> ###Voyage <br/> * is_nid * ss_type * ds_field_depart_date * is_field_destination * tm_field_master * is_field_origin * is_field_vessel * is_field_voyage_year * tm_title <br/> ###Vessel <br/> * is_nid * ss_type * tm_title * tm_field_services * im_field_sources * is_field_year_end * is_field_year_start * is_field_built_by * is_field_built_where * is_field_built_year * tm_field_demise * tm_field_rig * tm_field_dimensions * tm_field_tonnage <br/> ###Source <br/> * is_nid * ss_type * tm_title * tm_field_location * tm_field_reference <br/> ###Port <br/> * is_nid * ss_type * tm_title <br/> ###Organisation <br/> * is_nid * ss_type * tm_title <br/> ###Photos <br/> * is_fid: Unique ID for a file * tm_field_citation: Includes copyright information * tm_field_file_image_title_text: Image title * tm_field_location: Location of the image * tm_field_source: Source of the image * is_file_usage_count: Number of times this file is used in passengersinhistory.sa.gov.au * im_file_usage_list: List of content that uses this file * ss_url: Url to the file 1
• **Community History Endpoints** **Organisations** http://data.history.sa.gov.au/communityhistory/organisations **News** http://data.history.sa.gov.au/communityhistory/news **Events** http://data.history.sa.gov.au/communityhistory/events **Blogs** http://data.history.sa.gov.au/communityhistory/blogs **Article Detail** The nid field on each of the items (listed using any of the above endpoints) can be used to get specific detail using the following endpoint: http://data.history.sa.gov.au/communityhistory/{nid} Replace {nid} with the nid obtained from one of the above endpoints. **Files** The nid field on each of the events (listed using any of the above endpoints) can be used to get associated files (including base64 values) using the following endpoint: http://data.history.sa.gov.au/communityhistory/{nid}/files Replace {nid} with the nid obtained from one of the above endpoints. **Taxonomy** http://data.history.sa.gov.au/communityhistory/taxonomy/{id} Replace {id} with the taxonomy term id (represented by target_id throughout content) 1
• **History Festival Endpoints** **Events** http://data.history.sa.gov.au/abouttime/events/{year} Replace {year} with 2013, 2014 or 2015 **Event Detail** The nid field on each of the events (listed using the 'Events' endpoint) can be used to get event specific detail using the following endpoint: http://data.history.sa.gov.au/abouttime/event/{year}/{nid} Replace {year} with 2013, 2014, 2015 or 2016 Replace {nid} with the nid obtained from one of the events listing. **Event Images** The nid field on each of the events (listed using the 'Events' endpoint) can be used to get event images (including base64 values) using the following endpoint: http://data.history.sa.gov.au/abouttime/event/{year}/{nid}/files Replace {year} with 2013, 2014, 2015 or 2016 Replace {nid} with the nid obtained from one of the events listing. 1
• Developer Portal. 1
• Executive employment at the History Trust of South Australia for the period 2011-12 to 2020-21 for annual reporting purposes. 1
• Fraud detection at History Trust of South Australia for annual reporting processes covers period 2011 - 2021 1
• Information surrounding internees sourced from http://www.wakefieldpress.com.au/product.php?productid=1201 and National Australian Archives 1
• Instructions are provided in the primary URL An example of a basic implementation can be viewed at http://data.history.sa.gov.au/gallery.php?collection=bondstudio&startindex=0 The example code can be downloaded from http://data.history.sa.gov.au/gallery.php.txt 1
• Instructions are provided in the primary URL An example of a basic implementation can be viewed at http://data.history.sa.gov.au/gallery.php?collection=collection&startindex=0 The example code can be downloaded from http://data.history.sa.gov.au/gallery.php.txt 1
• Public complaints received by History Trust of South Australia for the period 2011-12 to 2020-21 for annual reporting purposes. 1
• Refer to main page for information surrounding the end points. Meta data and images can be accessed through the API. An example of a basic implementation can be viewed at http://data.history.sa.gov.au/gallery.php?collection=sagpc&startindex=0 The example code can be downloaded from http://data.history.sa.gov.au/gallery.php.txt 1
• Whistleblower disclosure at the History Trust of South Australia for the periods 2011-12 to 2017-21. 1
• Workplace Injury Claims received by History Trust of South Australia for period 2019-20 for annual reporting purposes. 1
• number if consultants engaged by the History Trust of SA for annual reporting purposes 1
• number of contractors engaged by the History Trust of SA 2019-20 1