Sources/FR/ACCO

From Dura Lex Wiki
Revision as of 01:55, 23 April 2026 by Nicolas (talk | contribs) (Source doc: acco — enterprise labor agreements (DILA) (via create-page on MediaWiki MCP Server))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Enterprise and branch labor agreements filed with the French Ministry of Labor. Metadata-rich (IDCC, unions, themes, company identifiers), often with attached .docx/.odt content files. See also kali for extended branch conventions.

Status: active

Source

[edit | edit source]
Key Kind Origin Auth Update
acco legislation DILA open data dump — echanges.dila.gouv.fr/OPENDATA/ACCO/ none incremental (tar.gz archives)

ID format: fr.{raw_id.lower()}

Coverage: 1900–present (includes forward-dated expiration)

Classification

[edit | edit source]
Tag Values
type collective_agreement (always)
document_form canonical_text (ACCORD), amendment (AVENANT), corrigendum (RECTIFICATIF)

Domain-specific

[edit | edit source]
Tag Notes
bargaining_level sectoral (CODE_UNITE_SIGNATAIRE in 01/02) or enterprise (others)
idcc convention collective identifier
themes list of theme labels
unions list of signatory unions
siret, siren company identifiers
company_name company denomination
activity_code APE/NACE code
sector industry sector
number agreement number
is_complete_version "true" if integral version

Dates

[edit | edit source]
Tag Notes
filing_date date filed with ministry
text_date date of the agreement text
effective_date entry into force
publication_date publication date
expiration_date end of validity (sentinel 2999-01-01 stripped)

date column: coalesced from filing_date > text_date > effective_date > publication_date.

Edges

[edit | edit source]

None.

[edit | edit source]
Source Relationship
kali Complementary. KALI = extended branch conventions with article-level granularity and enforcement tracking. ACCO = filed agreements with company-level metadata.

Limitations

[edit | edit source]
  • No enforcement_status tracking (unlike KALI)
  • No article-level granularity — each agreement is a single document
  • Content often in .docx/.odt attachments, not structured XML
  • No edges