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
Really difficult to offer something that fits to all companies - it really varies IMO based on the nature of the business. Creative Studios usually have a very different way of working compared to a bank. Also small companies have different needs compared to big organizations.
I have been working on this a bit on my own, but if anyone has some input (or even better real-world examples), please contribute, even if it is just a comment in this issue.
From my personal experience: Companies have a MESS regards to data organization. You really need to establish some kind of person that keeps things organized and makes sure everyone is following the rules.
Perhaps a style guide for business use. Directives such as:
never name a folder with 'new' or 'old'. Instead include a date.
Use consistent date format such as 2024q3 or YYYY-MM-DD instead of m-d-yy.
Having an explanative or descriptive file named README.TXT (or other standardized name) that explains the purpose of the collection of files - project/ticket #, creator, estimated archive/deprecation date, history.
By documenting for the long term, and being aware that staff come and go (or simply forget things), then any business data will benefit regardless of the actual folder structure and subdirectory names.
The text was updated successfully, but these errors were encountered: