You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often field notes contain unprofessional language that should not be included in the final digital product. Check against a publicly maintained list of profanity via API to make sure the language used is professional.
The text was updated successfully, but these errors were encountered:
However, uploading data and metadata via an API either as text chunks or whole files is probably not a good idea given concerns about sensitive data.
It would be easy to generate a simple profanity filter (I'm assuming most profanity slips through by mistake/oversight and not as an attempt to circumvent a profanity filter), but that would require maintaining a list of profane language... probably not something we want to do.
Often field notes contain unprofessional language that should not be included in the final digital product. Check against a publicly maintained list of profanity via API to make sure the language used is professional.
The text was updated successfully, but these errors were encountered: