Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔧 [Refactor] Use api.offenegesetze.de for BGBl #40

Open
darkdragon-001 opened this issue Apr 17, 2021 · 7 comments
Open

🔧 [Refactor] Use api.offenegesetze.de for BGBl #40

darkdragon-001 opened this issue Apr 17, 2021 · 7 comments
Labels

Comments

@darkdragon-001
Copy link
Collaborator

âš¡ Refactor ticket

Use api.offenegesetze.de instead of BGBl scraper.

Motive

Stable API instead of scraping a changing website.

@stefanw
Copy link
Member

stefanw commented Apr 17, 2021

This is generally a good idea. Just for your understanding that this new 'stable API' by OffeneGesetze.de is based on the same code as the one in this repo – so also scrapes a changing website. But that's how we do Open Data in Germany. 😬

@darkdragon-001
Copy link
Collaborator Author

@stefanw Where exactly is the scraper code located? offenegesetze.de or api.offenegesetze.de or something else?

At least I think that maintaining one scraper should be enough for this Github organization^^

Does anyone have some insights which laws are only published on Bundesanzeiger and not on Bundesgesetzblatt? Is the Bundesanzeiger scraper still necessary?

@stefanw
Copy link
Member

stefanw commented Apr 17, 2021

I believe the API is still powered by this little repo: https://github.com/stefanw/bgbl

However, starting soon (latest January 2022) the whole BGBl process will change (see update at the top of the post).

@darkdragon-001
Copy link
Collaborator Author

darkdragon-001 commented Apr 17, 2021

I believe the API is still powered by this little repo: https://github.com/stefanw/bgbl

😮 why did I fix the bgbl scraper in this repo some weeks ago (in #20 and #31) when you already fixed it before... We should definitely collaborate better and make sure we don't do the same work twice...

What do you think of moving your repository into this organization?

We are also discussing in #36 to split this repository up a bit. What are your ideas on this?

However, starting soon (latest January 2022) the whole BGBl process will change (see update at the top of the post).

Interesting and kudos for this success!

Where do you store the results and feed the api from?

Are there any plans to include publications from Bundesanzeiger on the offenegesetze.de website and API?

@ulfgebhardt
Copy link
Member

I would vote against a dependency on https://offenegesetze.de/daten that just seems to be scraping with extra steps. By putting another layer in between things break more easily.

I believe the best course of action would be to maintain a common & public scraper, which is used by all parties involved.

And furthermore I find it quite weird that you do not maintain that stuff in this repo @stefanw - thats what it was made for??!

@stefanw
Copy link
Member

stefanw commented Apr 18, 2021

We should definitely collaborate better and make sure we don't do the same work twice...

Sorry, I do not follow the work here too closely, so I missed the PRs.

What do you think of moving your repository into this organization?

I should definitely move it from my personal account, but maybe I should integrate it into api.offenegesetze.de? Right now it works for the purposes of that API and should only receive fixes when it breaks.

Where do you store the results and feed the api from?

@okfde runs a server with the offenegesetze infrastructure. (Or am I misunderstanding your question?)

Are there any plans to include publications from Bundesanzeiger on the offenegesetze.de website and API?

There were some loose plans for other law gazettes, but Bundesanzeiger (only Amtlicher Teil?) is likely better covered elsewhere.

@darkdragon-001
Copy link
Collaborator Author

What do you think of moving your repository into this organization?

I should definitely move it from my personal account, but maybe I should integrate it into api.offenegesetze.de? Right now it works for the purposes of that API and should only receive fixes when it breaks.

I would prefer not to maintain two scrapers of the same data. What is the output of your scraper? Maybe we can agree on a common format. What concerns this repository, we are pretty open on the format. I guess you already split the data based on years or months and run it regularly instead of the huge single json file output by this repository's scraper which we want to get rid of anyways...

Where do you store the results and feed the api from?

@okfde runs a server with the offenegesetze infrastructure. (Or am I misunderstanding your question?)

How is it stored? Folder of json's? Database? Something else?

Are there any plans to include publications from Bundesanzeiger on the offenegesetze.de website and API?

There were some loose plans for other law gazettes, but Bundesanzeiger (only Amtlicher Teil?) is likely better covered elsewhere.

Yes, from what I see, we only need Amtlicher Teil. It is still mentioned quite often in the sources from gesetze-im-internet.de...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants