Update README.md
Browse files
README.md
CHANGED
|
@@ -84,6 +84,18 @@ The following fields were extracted and/or transformed from the original source:
|
|
| 84 |
- `text`: chunk of the main text content.
|
| 85 |
- `chunk_text`: generated by concatenating `full_title`, article `number`, formatted `subtitles` and `text`.
|
| 86 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 87 |
### ✂️ 2. Generation of 'chunk_text'
|
| 88 |
|
| 89 |
Each article is naturally isolated and has its own `cid` value. But in case the article is too long, we have to split it in several chunks.
|
|
|
|
| 84 |
- `text`: chunk of the main text content.
|
| 85 |
- `chunk_text`: generated by concatenating `full_title`, article `number`, formatted `subtitles` and `text`.
|
| 86 |
|
| 87 |
+
- **List-based fields**:
|
| 88 |
+
- `links`: list of legal relationships associated with the article, extracted from the LEGI metadata.
|
| 89 |
+
Each element is a JSON object describing a link to another legal document (source or target), with fields such as:
|
| 90 |
+
- `title`: official title of the related document.
|
| 91 |
+
- `doc_id` / `text_doc_id`: LEGI or JORF identifier of the related document.
|
| 92 |
+
- `number` / `text_number`: article or act number when applicable.
|
| 93 |
+
- `category`: type of the related document (e.g. `LOI`, `DECRET`, etc.).
|
| 94 |
+
- `link_type`: nature of the relationship (e.g. `TXT_SOURCE`, `CITATION`).
|
| 95 |
+
- `link_direction`: direction of the relation (`source` when the current article cites another text, `cible` when it is cited by another text).
|
| 96 |
+
- `nor`: NOR identifier of the related act, when available.
|
| 97 |
+
- `text_signature_date`: signature date of the related text (YYYY-MM-DD), when available.
|
| 98 |
+
|
| 99 |
### ✂️ 2. Generation of 'chunk_text'
|
| 100 |
|
| 101 |
Each article is naturally isolated and has its own `cid` value. But in case the article is too long, we have to split it in several chunks.
|