llrs / llrs/DOGC

How to do this?

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

See if it is possible to do that based on an xml file downloaded from:
https://dogc.gencat.cat/es/pdogc_canals_interns/pdogc_resultats_fitxa/?action=fitxa&documentId=883774&language=es_ES
https://portaljuridic.gencat.cat/eli/es-ct/o/2020/10/08/arp170/dof/xml
https://portaljuridic.gencat.cat/eli/es-ct/o/2016/12/23/arp353/con/20201014

There isn't any open data format that is easy that I could find of

```
https://portaljuridic.gencat.cat/doc/es-ct/edict/2020/10/01/(16)/dof(16)/doc/{jurisdiction}/{type}/{year}/{month}/{day}/{number}/{version}/{version_date}/{language}/{format}
```

```
https://portaljuridic.gencat.cat/eli/es-ct/o/2020/10/08/arp170/dofarp170/eli/{jurisdiction}/{type}/{year}/{month}/{day}/{number}/{version}/{version_date}/{language}/{format}
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the XML responses from the three linked DOGC and Portal Jurídic URLs, focusing on the EADOP fields and URI schemas shown in the issue. Determine whether the source can be downloaded and transformed into a computer-feasible format; document the supported input and resulting output when that is established.

Written by the indexing model from the issue text.

Assessment

Tech stack
xml
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.