Skip to content

227 allow unretrieved#395

Merged
yolile merged 7 commits into
mainfrom
227-allow-unretrieved
Jun 5, 2025
Merged

227 allow unretrieved#395
yolile merged 7 commits into
mainfrom
227-allow-unretrieved

Conversation

@yolile
Copy link
Copy Markdown
Member

@yolile yolile commented Apr 8, 2025

@yolile yolile requested a review from jpmckinney April 8, 2025 13:52
@yolile
Copy link
Copy Markdown
Member Author

yolile commented Apr 8, 2025

I will add the translations once we agree on the text. And I'm not sure why the migration is failing (there is no a "0063_" file)

Copy link
Copy Markdown
Member

@jpmckinney jpmckinney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll make these and other changes.

Comment thread data_registry/admin.py Outdated
Comment thread data_registry/forms.py Outdated
Comment thread data_registry/models.py Outdated
Comment thread data_registry/models.py Outdated
@jpmckinney
Copy link
Copy Markdown
Member

I've removed the "closes" word from the issue description, because to close #227 we need to create the datasets. (#227 mentions México APF and Croatia – not sure if still relevant).

I think the "no data" warning might work better by replacing the "access data" section, since that is where users are likely to look.

Screenshot 2025-05-18 at 1 16 35 AM

@yolile yolile merged commit 6ac95f0 into main Jun 5, 2025
18 checks passed
@yolile yolile deleted the 227-allow-unretrieved branch June 5, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants