PUBLIC DATA IMPORT · Workflow idea

Bring a public data file into a list your team can review.

A published data file can provide useful information for a team’s shared spreadsheet. Retrieve the selected file, choose the records that meet the agreed country and reporting-period rules, create a stable way to recognize each row, and review the resulting updates.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A public data file
Produces
A spreadsheet updated with the selected 2023 country-week records, with a consistent matching value to help avoid repeated rows.
Category
Data

01 / The starting point

A clear request.
A useful direction.

A CSV available from a selected public source, containing country and reporting-week records

“Review the published testing data, keep records for Germany, Austria, and Switzerland from 2023, identify each country-week entry consistently, and add or update its spreadsheet row.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a team bring a defined slice of publicly available tabular information into a spreadsheet for review and use.

  1. Confirm the public source and reporting scope

    Check that the selected file is the intended testing dataset and that the team needs 2023 records for the three agreed countries.

  2. Review the country and week fields

    Make sure country identifiers and reporting weeks are clear enough to apply the team’s selection rule.

  3. Select the matching records

    Keep entries for Germany, Austria, and Switzerland within the 2023 reporting period and set aside other rows.

  4. Match records to existing spreadsheet rows

    Use a consistent country-and-week identity to find an existing entry or determine that a row is new.

  5. Update and verify the shared list

    Add new entries or refresh their existing rows, then review a sample and the total number of selected records.

03 / The result

Something useful.
Something to build on.

A spreadsheet updated with the selected 2023 country-week records, with a consistent matching value to help avoid repeated rows.

AmbactiWorkflow folio · 5 steps

Import a public CSV into a shared list

Data · Example outcome

The handoff

A spreadsheet updated with the selected 2023 country-week records, with a consistent matching value to help avoid repeated rows.

Keep in mind

Public data can change, omit context, or arrive in an unfamiliar format. Confirm the source and reporting period, check country and week values, and review the resulting row count before relying on the spreadsheet.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Select the public file and destination spreadsheet

Choose the source maintained for this data and the shared sheet where approved records should appear.

Set country, year, and record identity rules

Document which countries and reporting weeks are in scope and how each country-week row is recognized.

Decide how new and existing rows are handled

Specify which spreadsheet fields may be updated and how records outside the selected scope are left alone.

Review a sample and its record count

Check records near the period boundary, confirm the country selection, and compare the result with the source before using it.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗