Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty vs. null database fields and cleanup #1585

Open
ahankinson opened this issue Aug 8, 2024 · 0 comments
Open

Empty vs. null database fields and cleanup #1585

ahankinson opened this issue Aug 8, 2024 · 0 comments

Comments

@ahankinson
Copy link
Member

A number of fields in the database have a significant number of empty string values when they should be null. Here's a few of them:

main_app_chant.manuscript_full_text
main_app_chant.image_link
main_app_chant.indexing_notes
main_app_chant.volpiano
main_app_chant.volpiano_notes
main_app_chant.volpiano_intervals
main_app_source.description
main_app_source.selected_bibliography
main_app_source.summary

That's not an exhaustive list.

In addition, a number of text fields start with a space or carriage return, and those should probably be stripped since they will cause problems with sorting. Particularly the 'manuscript_full_text' and 'manuscript_full_text_std_spelling' columns.

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

No branches or pull requests

1 participant