Nectarine

also no im not employed yet, applied to like 38 companies in the past week

my day has been shit so your email totally cheered me up

sup noodi, are you employed yet, you rascal

starchaser was listening 3 months ago

NOODI!!

aer you glad you asked?

i guess the real answer is: evaluate your database structure, because if someone says "they didn't tidy up!" that's a REVIEW, that's a separate object from either the person, or the place where they visited.

hey you drunk human

("colour" in the widest sense. my semi-boss can't tell red from green. but ya know.)

but really i'd suggest the colour scheme thing if you have time and money

the idea is that anything with USER in the name probably isn't gonne be seen outside of client

User comments: Any internal user comments about this particular copy, e.g. "needs rebinding". We may at some future time want to turn comments into a list of tasks needing attention, either in the form of a report or [blah blah]

Notes: Any notes about this particular copy [of a book], e.g. "signed by the author" These are public notes that will be shown on the Web site.

there is an internal understanding that "user" means them (staff, client)as opposed to "visitor" (who is coming from the internet)

star: ok, i found it. we did this by putting the word "user" in the caption

Not that we intend to write terrible things in it, but stuff like "Didn't clean up after themselves. May have taken a tool home. Do not grant a membership again."

it publicly.:)

It's going to be separated in the UI at least in its own section of sorts when editing users, and labeled with a note about it being internal only. So this was just more for making sure when writing stuff me (or another later person) doesn't end up showing

"2017-01 People database development (revised).docx" i think this is the one!!

if you have a BIG budget then you can split it visually but we didin't

but can't remember what we went with, trying to find it

i have done exactly that

internalComments sounds good, though

coneofsilence

I'm leaning towards "internalComments"

Hmm. If you had a field that was for internal ("office use only") comments about a thing or person, would you just call it "comments" or something like "privateComments" to denote when referenced it shouldn't be shown to the person it's about?

NightRadio (Alexander Zolotov) Now that's interesting...

and btw you could tag songs with #sunvox, why not

no, just an open project http://www.warmplace.ru

doesn't usuallyt matter if the "producing" tool (music maker, compiler) eats lots of time and space, you just need to produce a tiny package for the target....