Revision as of 14:36, 30 August 2017

Request url: https://api.archivesportaleurope.net/services/search/eac-cpf. This service is a POST-request.

This search-service delivers a list of authority records for Corporate Bodies, Persons or Families (CPF) with the requested searchterm. A web developer is able to filter results on various facets.

Request parameters

Three request parameters can be used to do a search in descriptions of records creators and two types of filters can be used.

Empty Request example

{
  "count": "5",
  "startIndex": 0,
  "query": "*",
  "filters": [
    {
      "facetFieldName": "string",
      "facetFieldIds": [
        "string"
      ]
    }
  ],
  "dateFilters": [
    {
      "dateFieldName": "string",
      "dateFieldId": "string"
    }
  ],
  "sortRequest": {
    "sortType": "asc",
    "fields": [
      "string"
    ]
  }
}

Basic Request example

{
  "count": "5",
  "startIndex": 0,
  "query": "Inlichtingendienst",
  "filters": [
    {
      "facetFieldName": "country",
      "facetFieldIds": [
        "7"
      ]
    }
  ],
  "dateFilters": [
    {
      "dateFieldName": "fromDate",
      "dateFieldId": "1800-01-01_2"
    }
  ],
  "sortRequest": {
    "sortType": "asc",
    "fields": [
      "string"
    ]
  }
}

This example searches for archival descriptions with the term "Inlichtingendienst" and filters on the facet "country" with id = 7 (identifier for "NETHERLANDS") and date-facet "fromDate" with id = "1800-01-01_2" (identifier for the period 1800-1999).

count

The resultlist is delivered in chunks of a certain size. Request parameter "count" describes the number of results that are in one chunk. Optional. Default value is 5.

startIndex

Request parameter "startIndex" enables you to select the results that you want to have. Counting starts at zero. If "count" = 5, the second chunk starts with startIndex 5, the following at startIndex 10, etc. Optional. Default value is 0.

query

Containing the search term(s). Required.

filters

Request parameter "filters" enables you to filter the result on facets. The facets are summarised in searchEac#facets.

dateFilters

Request parameters "dateFilters" enables you to filter the result on a certain period of time. The dateFacets are summarised in searchEac#date_facets

sortRequest

Request parameters "sortRequest" enables you to sort the result. The sortRequest contains two parameters: sortType and fields.

In "fields", you can provide a list of 1 or more fields. The resultlist is ordered on field[0] first, field[1] secondly, etc. The possible fields are:

• date: date of the archival material, provided in <existDates>

In all situations you can sort ascending or descending by setting request parameter "sortType" "asc" or "desc" respectively.

Response parameters

The response contains a list of the descriptions where the requested search term(s) was/were found.

Empty Response example

{
  "totalResults": 0,
  "startIndex": 0,
  "totalPages": 0,
  "eacSearchResults": [
    {
      "id": "string",
      "recordId": "string",
      "entityType": "string",
      "nameEntries": [
        "string"
      ],
      "nameEntriesWithHighlighting": [
        "string"
      ],
      "existDates": "string",
      "description": "string",
      "descriptionWithHighlighting": "string",
      "other": "string",
      "otherWithHighlighting": "string",
      "repository": "string",
      "repositoryCode": "string",
      "country": "string",
      "countryId": "string",
      "numberOfArchivalMaterialRelations": "string",
      "numberOfNameRelations": "string"
    }
  ],
  "sortFields": [
    "string"
  ],
  "facetFields": {
    "country": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "repository": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "entityType": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "place": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "language": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "unitDateType": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ]
  },
  "facetDateFields": {
    "fromDate": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ],
    "toDate": [
      {
        "id": "string",
        "name": "string",
        "frequency": 0
      }
    ]
  }
}

Basic Response example

Response for the basic request example above:

{
  "totalResults": 1,
  "startIndex": 0,
  "totalPages": 1,
  "eacSearchResults": [
    {
      "id": "26005",
      "recordId": "489d662d-b214-4b7a-98e2-d01b253c773f",
      "entityType": "corporatebody",
      "nameEntries": [
        "Militaire Inlichtingendienst (Defensie)",
        "MID",
        "Militaire Inlichtingendienst (2)"
      ],
      "nameEntriesWithHighlighting": [
        "Militaire <em>Inlichtingendienst</em> (Defensie)"
      ],
      "existDates": "1988 - 2002",
      "description": " In 1988 ontstaan uit samenvoeging van de Marine Inlichtingendienst (MARID), de Landmacht Inlichtingendienst (LAMID) en de Luchtmacht Inlichtingendienst (LUID). Rijksoverheid De Militaire Inlichtingendienst heeft in het belang van de nationale veiligheid tot taak:  het verrichten van onderzoek omtrent het potentieel en de strijdkrachten van andere mogendheden, ten behoeve van een juiste opbouw en een doeltreffend gebruik van de krijgsmacht en naar factoren die van invloed zijn of kunnen zijn op de handhaving en bevordering van de internationale rechtsorde voor zover de krijgsmacht daarbij is betrokken of naar verwachting betrokken kan worden;  het verrichten van veiligheidsonderzoeken als bedoeld in de Wet veiligheidsonderzoeken;  het verrichten van onderzoek dat nodig is voor het treffen van maatregelen ter voorkoming van activiteiten die ten doel hebben de veiligheid of paraatheid van de krijgsmacht te schaden, ter bevordering van een juist verloop van mobilisatie en concentratie der strijdkrachten en ten behoeve van een ongestoorde voorbereiding en inzet van de krijgsmacht.  het bevorderen van maatregelen ter bescherming van de onder c genoemde belangen, waaronder begrepen maatregelen ter beveiliging van gegevens betreffende de krijgsmacht waarvan de geheimhouding is geboden;  het verrichten van onderzoek betreffende andere landen, ten aanzien van onderwerpen met een militaire relevantie die door Onze Minister-President, Minister van Algemene Zaken, in overeenstemming met Onze betrokken Ministers, zijn aangewezen;  het opstellen van dreigingsanalyses op verzoek van Onze Minister van Binnenlandse Zaken en Koninkrijksrelaties en Onze Minister van Veiligheid en Justitie gezamenlijk ten behoeve van de beveiliging van de personen, bedoeld in de artikelen 4, derde lid, onderdeel b, en 42, eerste lid, onder c, van de Politiewet 2012 en de bewaking en de beveiliging van de objecten en de diensten die zijn aangewezen op grond van artikel 16 van die wet, voor zover het betreft personen, objecten en diensten met een militaire relevantie.",
      "descriptionWithHighlighting": " In 1988 ontstaan uit samenvoeging van de Marine <em>Inlichtingendienst</em> (MARID",
      "other": " Algemene Leiding (Defensie) Militaire Inlichtingen- en Veiligheidsdienst (Defensie) Marine Inlichtingendienst (Defensie) Landmacht Inlichtingendienst (Defensie) Luchtmacht Inlichtingendienst (Defensie)",
      "otherWithHighlighting": ") Marine <em>Inlichtingendienst</em> (Defensie) Landmacht <em>Inlichtingendienst</em> (Defensie",
      "repository": "Nationaal Archief",
      "repositoryCode": "NL-HaNA",
      "country": "NETHERLANDS",
      "countryId": "7",
      "numberOfArchivalMaterialRelations": "0",
      "numberOfNameRelations": "5"
    }
  ],
  "sortFields": [
    "date"
  ],
  "facetFields": {
    "country": [
      {
        "id": "7",
        "name": "NETHERLANDS",
        "frequency": 1
      }
    ],
    "repository": [
      {
        "id": "2437",
        "name": "Nationaal Archief",
        "frequency": 1
      }
    ],
    "entityType": [
      {
        "id": "corporatebody",
        "name": "corporatebody",
        "frequency": 1
      }
    ],
    "place": [],
    "language": [
      {
        "id": "dut",
        "name": "dut",
        "frequency": 1
      }
    ],
    "unitDateType": [
      {
        "id": "normal",
        "name": "normal",
        "frequency": 1
      }
    ]
  },
  "facetDateFields": {
    "fromDate": [
      {
        "id": "1980-01-01_3",
        "name": "1980-1999",
        "frequency": 1
      }
    ],
    "toDate": [
      {
        "id": "2000-01-01_2",
        "name": "2000-2199",
        "frequency": 1
      }
    ]
  }
}

totalResults

The response parameter "totalResults" gives the number of results.

startIndex

The response parameter "startIndex" gives the number of the chunk you requested.

totalPages

The response parameter "totalPages" gives the number of chunks.

eacSearchResults

Enumeration of the results. They are all optional except "id".

sortFields

This response parameter sums up the various fields you can use to order the resultList in a, new, additional request (see: searchEac#sortRequest):

• date

facetFields

This response parameter gives an enumeration of facets. Every facet has three variables.

facets

date facets

With the date facets you can zoom in on the period of time. Results are grouped in periods of two centuries in the first step. If you use these groupings in the request-parameter dateFilter, you'll have new dateFacets that groups the results into groups of two decades.