I voted for this because if it is what I think it is I want it. But what do you really mean by logging procedures?

I am suggesting to create a procedures guide within the database, similar to the help topics. This way anyone who is working within the database can search on how information should be added, updated, exported or reported.

Oh then I thought it was something else. You can create documents you can add to people's favorites but they would not be searchable. I have all of my documents on our internal sharepoint site so I do not need this.

This title is too vague. I think this is what I want but I am not sure. I want to be able to click on any field in any record to open a user-defined log where I can record our organization-specific policies relating to how/what to record in corresponding fields. Further to this, I want a branch on the Help drop-down menu where I can store my organization-specific procedure documents right in RE.

Jennifer, I was thinking of what you mentions: " I want to be able to click on any field in any record to open a user-defined log where I can record our organization-specific policies relating to how/what to record in corresponding fields. Further to this, I want a branch on the Help drop-down menu where I can store my organization-specific procedure documents right in RE."

Probably not too many here are into Database Theory, but one of the principles is that all information about the database is contained within the database. This would be along those lines. I agree.

They had this is eTapestry and it was a very convenient place to store and find the procedures

This is a really great idea. If I'm going to create policies and procedures for how to do anything in RE, it would be nice to store those items within RE.

I'd love to see something like this for attributes too. An attributes "key" that defines what all the attributes are, when they were created, and what they are used for. There's always turnover at organizations and unless you are following someone who did a great job at documenting this kind of information and happened to know what happened before her/his time, you won't necessarily know what is going on with your database.

Personally I just have relative manuals/policies/procedures in a one note document which is 100% searchable. As much as I like this idea I would imagine that there is a lot of limitations with blackbaud.