Skip to content

Attribution Requirements

This document provides comprehensive guidance on proper attribution requirements for data accessed through Denmark's Parliamentary Open Data API (oda.ft.dk). Following proper attribution practices ensures compliance with Danish open data standards and supports transparency in democratic data usage.

Attribution Requirements Overview

Mandatory Attribution

All usage of data from Denmark's Parliamentary Open Data API requires proper attribution, regardless of the context or purpose. This applies to:

  • Academic research and publications
  • Commercial applications and services
  • Data journalism and media reporting
  • Government and institutional usage
  • Personal projects and analysis
  • Educational materials and presentations

Attribution requirements are based on: - Danish Open Data Standards (Fællesoffentlig digitaliseringsstrategi) - EU Open Data Directive (2019/1024/EU) - Parliamentary transparency obligations - Academic and professional citation standards

Mandatory Attribution Elements

Core Attribution Components

Every attribution must include these essential elements:

Source: Danmarks Folketing Open Data API (oda.ft.dk)
Data Provider: Folketinget (Danish Parliament)  
Access Date: [YYYY-MM-DD]
API Endpoint: [specific endpoint used]

Complete Attribution Template

Data Source: Danmarks Folketing Open Data API
Provider: Folketinget (Danish Parliament)
URL: https://oda.ft.dk/api/
Accessed: [DATE]
Endpoint: [SPECIFIC_ENDPOINT]
License: Open Data under Danish transparency legislation

Minimal Attribution Format

For space-constrained contexts:

Source: Folketinget Open Data (oda.ft.dk), accessed [DATE]

Source Citation Standards

Academic Citation Formats

APA Style (7th Edition)

Folketinget. (YYYY, Month DD). Parliamentary data [Data set]. 
Danmarks Folketing Open Data API. https://oda.ft.dk/api/[endpoint]

Example:

Folketinget. (2024, March 15). Parliamentary cases and voting records [Data set]. 
Danmarks Folketing Open Data API. https://oda.ft.dk/api/Sag

Chicago Style (Author-Date)

Folketinget. "Parliamentary Data." Danmarks Folketing Open Data API. 
Accessed March 15, 2024. https://oda.ft.dk/api/[endpoint].

Harvard Style

Folketinget (2024) Parliamentary data, Danmarks Folketing Open Data API. 
Available at: https://oda.ft.dk/api/[endpoint] (Accessed: 15 March 2024).

Bibliographic Citation Examples

For Parliamentary Cases

Folketinget (2024) Sag data [Parliamentary cases], Danmarks Folketing Open Data API, 
oda.ft.dk/api/Sag (Accessed: [DATE])

For Voting Records

Folketinget (2024) Afstemning data [Voting records], Danmarks Folketing Open Data API, 
oda.ft.dk/api/Afstemning (Accessed: [DATE])

For Actor Information

Folketinget (2024) Aktør data [Parliamentary actors], Danmarks Folketing Open Data API, 
oda.ft.dk/api/Aktor (Accessed: [DATE])

Academic and Research Attribution

Research Paper Attribution

In-Text Citations

According to data from Denmark's Parliamentary Open Data API (Folketinget, 2024)...

Parliamentary voting patterns show (Danmarks Folketing Open Data, accessed March 2024)...

Methodology Sections

Data Collection: Parliamentary data was obtained through Denmark's Open Data API 
(https://oda.ft.dk/api/) maintained by Folketinget. The dataset includes [description] 
accessed on [DATE] using the following endpoints: [list endpoints].

Attribution: All data is attributed to Folketinget (Danish Parliament) through 
their official Open Data API as required by Danish transparency legislation.

Data Availability Statements

Data Availability: The datasets analyzed in this study are publicly available 
through Denmark's Parliamentary Open Data API (https://oda.ft.dk/api/). 
Data can be accessed without authentication. Specific queries and endpoints 
used in this research are documented in the supplementary materials.

Thesis and Dissertation Attribution

Data Sources Section

Primary Data Source: Danmarks Folketing Open Data API
- Provider: Folketinget (Danish Parliament)
- URL: https://oda.ft.dk/api/
- Coverage: Parliamentary sessions 2009-2024
- Access Period: January-March 2024
- License: Open Data under Danish transparency legislation
- Attribution Requirement: All derived works must attribute source to Folketinget

Acknowledgments Section

The author acknowledges Folketinget (Danish Parliament) for providing open access 
to parliamentary data through their comprehensive Open Data API (oda.ft.dk). 
This research was made possible by Denmark's commitment to governmental transparency 
and open data initiatives.

Commercial Application Attribution

Web Applications and Services

<!-- Required attribution -->
<div class="data-attribution">
    Parliamentary data provided by 
    <a href="https://oda.ft.dk">Folketinget Open Data API</a>
    | Last updated: [DATE]
</div>

About/Credits Page

## Data Sources

This application uses open parliamentary data provided by Folketinget 
(Danish Parliament) through their official Open Data API.

- **Data Provider:** Folketinget (Danish Parliament)
- **API URL:** https://oda.ft.dk/api/
- **License:** Open Data under Danish transparency legislation
- **Attribution:** Required for all derivative works
- **Last Accessed:** [DATE]

We acknowledge Folketinget's commitment to transparency in making this 
valuable democratic data freely available to researchers, developers, 
and citizens.

Mobile Applications

Settings/About Attribution

DATA SOURCES

Parliamentary Data:
Source: Folketinget Open Data API
Provider: Danish Parliament (Folketinget)  
URL: oda.ft.dk
License: Open Data
Updated: [DATE]

This app is built using open governmental data made available through 
Denmark's commitment to transparency and democratic accountability.

API Documentation Attribution

# API documentation example
data_sources:
  parliamentary_data:
    provider: "Folketinget (Danish Parliament)"
    source: "Danmarks Folketing Open Data API"  
    url: "https://oda.ft.dk/api/"
    license: "Open Data"
    attribution_required: true
    last_updated: "2024-03-15"
    note: "All derivative works must attribute data source to Folketinget"

Digital and Web-Based Attribution

Website Integration

Header Attribution (Prominent Display)

<div class="data-source-banner">
    <i class="icon-data"></i>
    Data from <strong>Folketinget Open Data API</strong> 
    | <a href="https://oda.ft.dk">oda.ft.dk</a>
    | Updated: [DATE]
</div>
<aside class="attribution-sidebar">
    <h3>Data Source</h3>
    <p>Parliamentary information provided by:</p>
    <ul>
        <li><strong>Folketinget</strong> (Danish Parliament)</li>
        <li><strong>API:</strong> oda.ft.dk</li>
        <li><strong>License:</strong> Open Data</li>
        <li><strong>Accessed:</strong> [DATE]</li>
    </ul>
    <p><small>Attribution required for all uses</small></p>
</aside>

Social Media Attribution

Twitter/X Posts

Parliamentary voting analysis based on @Folketinget open data 
(oda.ft.dk) #OpenData #DanishPolitics #Transparency

LinkedIn Posts

Analysis based on open parliamentary data from Folketinget 
(Danish Parliament) via their Open Data API: https://oda.ft.dk

Denmark's commitment to governmental transparency enables valuable 
democratic research and citizen engagement.

Blog Post Attribution

Standard Blog Attribution

---
title: "Parliamentary Analysis"  
data_source: "Folketinget Open Data API"
data_url: "https://oda.ft.dk/api/"
accessed_date: "2024-03-15"
---

*Data Source: This analysis uses parliamentary data from Folketinget 
(Danish Parliament) through their Open Data API (oda.ft.dk). 
Data accessed March 15, 2024.*

Attribution in Data Visualizations

Chart and Graph Attribution

Data Source: Folketinget Open Data API (oda.ft.dk) | Accessed: [DATE]

Detailed Visualization Attribution

Source: Danmarks Folketing Open Data API
Provider: Folketinget (Danish Parliament)
Endpoint: oda.ft.dk/api/[specific]
Data Period: [RANGE]
Accessed: [DATE]
License: Open Data

Interactive Dashboard Attribution

Dashboard Header

<div class="dashboard-attribution">
    <h2>Parliamentary Data Dashboard</h2>
    <p class="data-credit">
        Data: <a href="https://oda.ft.dk">Folketinget Open Data API</a>
        | Real-time parliamentary information
        | Last updated: <span id="last-update">[DATE]</span>
    </p>
</div>

Tooltip Attribution

// JavaScript tooltip with attribution
const tooltip = {
    footer: "Source: Folketinget Open Data (oda.ft.dk)",
    style: { fontSize: '10px', color: '#666' }
};

Infographic Attribution

Visual Attribution Block

=Ê DATA SOURCE
Folketinget Open Data API
oda.ft.dk | Accessed [DATE]

<Û PROVIDED BY  
Danish Parliament (Folketinget)
Open governmental data initiative

Reports and Documentation Attribution

Executive Summary Attribution

DATA DISCLAIMER AND ATTRIBUTION

This report utilizes open parliamentary data provided by Folketinget 
(Danish Parliament) through their official Open Data API (oda.ft.dk). 
All data analysis and interpretations are those of the authors and do 
not represent official positions of Folketinget.

Data accessed: [DATE RANGE]
API endpoints used: [LIST]
License: Open Data under Danish transparency legislation

Technical Report Attribution

Data Sources Section

## 2.1 Data Sources and Attribution

### Primary Data Source
- **Provider:** Folketinget (Danish Parliament)
- **Source:** Danmarks Folketing Open Data API  
- **URL:** https://oda.ft.dk/api/
- **Coverage Period:** 2009-2024
- **Total Records:** 96,538+ cases, 18,139+ actors
- **Access Method:** RESTful API with OData 3.0 protocol
- **Authentication:** None required (public data)
- **Rate Limiting:** Standard API limits apply
- **Data Format:** JSON, XML available
- **Update Frequency:** Real-time for current sessions

### Attribution Requirements
All derivative works, analysis, and publications using this data must 
include proper attribution to Folketinget as the data provider, in 
accordance with Danish open data standards and transparency obligations.

### Data Quality and Completeness
The dataset provides comprehensive coverage of Danish parliamentary 
proceedings with high data quality maintained by Folketinget's 
information systems. Users should verify current data availability 
and any updates to data structures through the API documentation.

Multi-Source Attribution Handling

Combined Data Sources

When Using Multiple APIs

DATA SOURCES:
1. Parliamentary Data: Folketinget Open Data API (oda.ft.dk)
2. Economic Data: [Other source]
3. Demographics: [Other source]

Primary Attribution: Folketinget (Danish Parliament) for all 
parliamentary information including cases, voting records, 
actor information, and legislative proceedings.

Multi-Dataset Attribution Table

| Data Type | Source | Provider | URL | Accessed |
|-----------|--------|----------|-----|----------|
| Parliamentary Cases | Folketinget Open Data API | Danish Parliament | oda.ft.dk/api/Sag | 2024-03-15 |
| Voting Records | Folketinget Open Data API | Danish Parliament | oda.ft.dk/api/Afstemning | 2024-03-15 |
| Actor Information | Folketinget Open Data API | Danish Parliament | oda.ft.dk/api/Aktor | 2024-03-15 |

Cross-Referenced Analysis

Parliamentary Analysis Attribution:
This analysis combines data from multiple sources. Parliamentary data 
(cases, votes, actors, documents) sourced from Folketinget Open Data API 
(oda.ft.dk). [Other sources as applicable]. Each dataset maintains 
separate attribution requirements as specified by respective providers.

Attribution Validation and Compliance

Automated Attribution Checking

Python Validation Script

def validate_attribution(content, required_elements):
    """
    Validate that content includes proper Folketinget attribution
    """
    required_elements = [
        'Folketinget',
        'oda.ft.dk',
        'Danish Parliament',
        'Open Data'
    ]

    missing_elements = []
    for element in required_elements:
        if element.lower() not in content.lower():
            missing_elements.append(element)

    return {
        'is_valid': len(missing_elements) == 0,
        'missing_elements': missing_elements,
        'recommendations': generate_attribution_suggestions()
    }

def generate_attribution_suggestions():
    return [
        "Include 'Folketinget' or 'Danish Parliament' as data provider",
        "Reference 'oda.ft.dk' as the API source",
        "Specify access date for transparency",
        "Include 'Open Data' license reference"
    ]

Attribution Compliance Checklist

## Attribution Compliance Checklist

### Required Elements 
- [ ] Data provider identified as "Folketinget" or "Danish Parliament"
- [ ] API source referenced as "oda.ft.dk" or full URL
- [ ] Access date specified (YYYY-MM-DD format)
- [ ] Open Data license acknowledgment
- [ ] Appropriate prominence for context

### Content-Specific Requirements 
- [ ] Academic: Proper citation format used
- [ ] Commercial: User-visible attribution included  
- [ ] Visualization: Chart/graph attribution present
- [ ] Website: Footer or about page attribution
- [ ] Report: Data sources section included

### Quality Standards 
- [ ] Attribution factually accurate
- [ ] No misleading claims about official endorsement
- [ ] Clear distinction between data and analysis
- [ ] Professional presentation appropriate to context

Manual Compliance Review

Pre-Publication Checklist

  1. Attribution Presence: Verify all required elements included
  2. Accuracy Check: Confirm API URL, provider name, dates correct
  3. Prominence Review: Ensure attribution appropriately visible
  4. Context Appropriateness: Attribution matches usage context
  5. Professional Standards: Attribution follows field conventions

Post-Publication Monitoring

Attribution Compliance Monitoring:
- Regular review of published content attribution
- Updates when API structure or requirements change
- Response to attribution correction requests
- Maintenance of attribution consistency across platforms

Best Practices and Common Mistakes

Attribution Best Practices

 DO: Correct Attribution Examples

 "Data from Folketinget Open Data API (oda.ft.dk), accessed March 2024"

 "Parliamentary information provided by Folketinget (Danish Parliament) 
   through their Open Data API: https://oda.ft.dk/api/"

 "Source: Danmarks Folketing Open Data API, endpoint: /api/Sag, 
   accessed 2024-03-15"

 Academic: "Folketinget. (2024). Parliamentary cases [Data set]. 
   Danmarks Folketing Open Data API. https://oda.ft.dk/api/Sag"

Professional Attribution Standards

  1. Clarity: Make attribution easily identifiable
  2. Accuracy: Use correct names, URLs, dates
  3. Completeness: Include all required elements
  4. Consistency: Maintain same attribution across project
  5. Appropriateness: Match attribution style to context
  6. Accessibility: Ensure attribution readable by target audience

L Common Attribution Mistakes

Incorrect Attribution Examples

L "Data from Danish government API" (too vague)

L "Parliamentary data (accessed sometime in 2024)" (imprecise date)

L "Source: ft.dk" (incorrect URL)

L "Official parliamentary information" (implies endorsement)

L "Government data - no attribution required" (incorrect license assumption)

L "Data: Denmark Parliament API" (informal/incorrect naming)

Frequent Attribution Errors

  1. Vague Attribution: Using generic terms instead of "Folketinget"
  2. Missing Dates: Omitting access date for transparency
  3. Wrong URLs: Using incorrect or shortened URLs
  4. Implied Endorsement: Suggesting official approval of analysis
  5. Hidden Attribution: Placing attribution in inaccessible locations
  6. Inconsistent Style: Varying attribution format within same work

Attribution Troubleshooting

When Attribution Space is Limited

Minimal attribution options:
- "Source: Folketinget (oda.ft.dk)"
- "Data: Danish Parliament API"  
- "Folketinget Open Data, 2024"

When Multiple Endpoints Used

"Data from multiple Folketinget Open Data API endpoints 
(oda.ft.dk/api/): Sag, Afstemning, Aktor. Accessed March 2024."

For Real-Time Data Integration

"Live parliamentary data from Folketinget Open Data API 
(oda.ft.dk). Data updated continuously during active sessions."

Attribution Quality Assurance

Review Questions

  1. Is the data provider clearly identified as Folketinget/Danish Parliament?
  2. Is the API source (oda.ft.dk) properly referenced?
  3. Are access dates specific and current?
  4. Does attribution match professional standards for the context?
  5. Is attribution prominently displayed for the audience?
  6. Are there any claims of official endorsement or approval?

Correction Process

When attribution errors are identified: 1. Immediate Fix: Correct attribution in live content 2. Documentation Update: Revise any documentation or guides 3. Communication: Inform stakeholders of correction if needed 4. Prevention: Update processes to avoid similar errors


Summary

Proper attribution for Denmark's Parliamentary Open Data API requires:

  • Clear identification of Folketinget as data provider
  • Specific reference to oda.ft.dk API source
  • Transparent dating of data access
  • Context-appropriate attribution style
  • Professional presentation matching usage context

Following these guidelines ensures compliance with Danish open data standards while supporting democratic transparency and accountability in data usage.

For questions about attribution requirements, consult the API documentation or contact Folketinget's data services team through official channels.