wetsuite.datacollect.koop_repositories.BWB

class documentation

class BWB(wetsuite.datacollect.sru.SRUBase):

View In Hierarchy

SRU endpoint for the Basis Wetten Bestand repository

See a description in https://www.overheid.nl/sites/default/files/wetten/Gebruikersdocumentatie%20BWB%20-%20Zoeken%20binnen%20het%20basiswettenbestand%20v1.3.1.pdf

Method __init__ base_url should be everything up to the ?

Inherited from SRUBase:

Method explain Does an explain operation, Returns the XML
Method explain_parsed Does an explain operation, Returns a dict with some of the more interesting details.
Method num_records After you do a search_retrieve, this should be set to a number.
Method search_retrieve Fetches a range of results for a particular query. Returns each result record as a separate ElementTree object.
Method search_retrieve_many This function builds on search_retrieve() to "fetch _many_ results results in chunks", by calling search_retrieve() repeatedly. (search_retrieve() will have a limit on how many to search at once, though is still useful to see e...
Instance Variable base_url Undocumented
Instance Variable extra_query Undocumented
Instance Variable number_of_records Undocumented
Instance Variable sru_version Undocumented
Instance Variable verbose Undocumented
Instance Variable x_connection Undocumented
Method _url Combines the basic URL parts given to the constructor, and ensures there's a ? (so you know you can add &k=v) This can probably go into the constructor, when I know how much is constant across SRU URLs...
def __init__(self, verbose=False):
overrides wetsuite.datacollect.sru.SRUBase.__init__

base_url should be everything up to the ?

Notes:

  • x_connection is used to specify the collection within a server, and seems to be non-standard and required
  • extra_query is used to let us AND something into the query, and is intended to restrict to a subset of documents in these cases, x_connection seems to include in extra sets, and the combination is sometimes too much (?)