Data Publication Rules for Vendors - Saint Paul

Vendors working with the City of Saint Paul, Minnesota must follow local data publication expectations that support transparency, procurement compliance, and Minnesota data practices. This guide summarizes what kinds of vendor-supplied data the city generally expects to be published or made available, where to check official datasets, and practical steps vendors should take when contracts or city policies require data publication. It explains enforcement and appeal routes, how to submit forms or requests, and how to report noncompliance to city offices. Use this page to prepare contract deliverables, meet open-data commitments, and reduce risk when providing services to Saint Paul.

What vendors must publish

Vendor obligations vary by contract and by the city’s open data expectations. Typical categories the city or its open data portal identifies for publication include:

• Contract deliverables and reports produced under a city agreement.
• Machine-readable datasets created or processed for city programs (CSV, JSON, geospatial files).
• Metadata, data dictionaries, and update frequency notes.
• Schedule or timeline for dataset publication and periodic updates.

For specific dataset categories, publication formats, and licensing preferences consult the City of Saint Paul open data portal and policy materials.Open Data Portal^[1]

Penalties & Enforcement

Enforcement for failure to comply with city data publication expectations depends on the controlling document: the contract terms, the city’s published open data policy, or applicable state law. The official sources do not always list fixed monetary fines for vendor data publication failures; where amounts or civil penalties are not published on the controlling page, the city typically enforces compliance through contract remedies and administrative processes.

• Fine amounts: not specified on the cited page for vendor data publication; contract remedies are primary.Procurement Services^[2]
• Escalation: first notice, cure period, then contractual withholding or termination are typical; exact timeframes are contract-specific and not specified on the cited page.
• Non-monetary sanctions: compliance orders, withholding of payments, contract suspension or termination, and referral to legal action or litigation.
• Enforcer and inspection: contract manager, Procurement Services, and the city technology/open-data office conduct reviews and accept submissions; state data practices issues may involve Minnesota statutory guidance.Minnesota Statutes, Chapter 13^[3]
• Appeals/review: appeal and dispute resolution usually follow contract dispute clauses or administrative protest procedures; specific time limits and appeal steps are set in the contract or procurement rules and are not always published on a single controlling page.
• Defences/discretion: compliance may be excused for lawful data privacy constraints, confidentiality under state law, or where a contract provides permitted delays, variances, or approved exemptions.

Applications & Forms

The city does not publish a universal vendor "data publication" form; dataset submissions are usually uploaded to the city open data portal or delivered via contract-specified methods. For procurement disputes or contract compliance filings use Procurement Services forms and protest procedures available on the city procurement page.Procurement Services^[2]

FAQ

Who decides what vendor data must be published?

Contracting departments and the city open data policy determine required datasets; procurement and the project contract specify deliverables.

Can vendors redact private information before publication?

Yes, vendors must follow Minnesota data practices law and contract confidentiality provisions; redact data only as allowed and document redactions.

Where do I report a vendor who failed to publish required data?

Report nonpublication to the contract manager listed in the contract and to Procurement Services; for statutory data-practices concerns consult the state statute link above.

How-To

1. Review your contract for open-data deliverables and any referenced data standards.
2. Prepare machine-readable files (CSV/JSON/GEOJSON) and a simple metadata file or data dictionary.
3. Validate data for personal or confidential information and apply required redactions per Minnesota law.
4. Upload datasets to the City of Saint Paul open data portal or deliver by the contract-specified method by the deadline.
5. If you cannot meet publication requirements, notify the contract manager and Procurement Services immediately and request an approved variance in writing.

Key Takeaways

• Check your contract and the city open data portal for specific dataset requirements.
• Use machine-readable formats and include metadata for every published dataset.
• Contact Procurement Services and the contract manager early if you expect delays or privacy conflicts.

Help and Support / Resources

• City of Saint Paul Open Data Portal
• City of Saint Paul Procurement Services
• Minnesota Statutes, Chapter 13 - Government Data Practices

1. [1] City of Saint Paul Open Data Portal
2. [2] City of Saint Paul Procurement Services
3. [3] Minnesota Statutes, Chapter 13