You are reading a single comment by @gbj_tester and its replies. Click here to read the full conversation.
  • Question for people with common sense and maybe some IT nous.

    I'm wanting to give our drives a spring clean - looking for best practices on folder structure, filesystem hierarchy etc from the top down. Needs to cater for:

    Management stuff (staff stuff, website masters, branding, various logos and assets,
    Finance stuff (tax, payroll, banking, accounts, receipts etc)
    Legal and contract stuff (both for clients and freelancers/employees)
    Development stuff (i.e. pitching and proposals, case studies)
    Client stuff (actual work - documents only, raw video and project files are stored locally on RAID)

    Common issues:
    Should client docs be on a project by project basis within the client folder? What about assets shared between projects?

    What happens with pitches when they get signed? I.e. move folder to client directory? Leave as is?

    We use Google Drive and create stuff with google docs/sheets etc - some clients share this practice, others use MS Office so we end up with various duplicates in Docx, PDF and GDoc form. Retain these? Delete them? We usually share google docs links while we're working on them. We usually send final docs to client as PDFs as standard unless they ask for docx versions.

    Is there a way with Google Drive (working on MacOS) to set a default location for new file creations OTHER than the top directory? Currently every time we open up Sheets or Docs or whatever it automatically saves it in the top directory and we have to move it to the corresponding client folder which is a faff, albeit a small one.

    Is there a way using Google Drive and MacOS to see previews of documents in Finder? I.e. I can see a preview of a .numbers or even a .xlsx file but not a .sheet - presume that's unlikely to change any time soon - should I switch everyone to PixelBooks (only half joking)

    Would also like to revisit naming conventions for files - been a really busy year and frankly we've all (myself included) been sloppy about naming things - i.e. starting Obviously a naming convention is only useful if people follow it but if I'm going to be stricter on getting people to do so I'd like to have some confidence that I'm asking people to follow the right one.

    Does anyone have some good reading material/links to go over? Or experiences of pitfalls etc.

    Can someone just do this for me? kthanxbai

  • looking for best practices on folder structure, filesystem hierarchy

    I used to think folder structure was important, but search is fast now.

    I think it's probably better to concentrate on tagging files rather than naming them.

  • Didn't even know tagging was possible within "g suite".

    Game for that idea though I do like seeing row after row of neatly named files :/

  • I used to think folder structure was important, but search is fast now.

    I think it's probably better to concentrate on tagging files rather than naming them.

    I don't know what job you do, but this is the sort of thing people say whose work all fits neatly on Github.

About

Avatar for gbj_tester @gbj_tester started