Wednesday, May 27, 2009

Separating strange data!

I had some inconsistent data that I needed to separate in to records. It was like a big block of Document history.

The code to update the document history was written by several developers, so it wasn't always logged in the same way..

One developer logged it like this:
Date -- Who took action - Action

Another developer logged it like this:
Who took action (date )
Status Changed: From old status to new status
Details: details
------------------------------------------------------

so.. I needed to export each update in the text as a separate row of data..

I messed around w/some sample data in button using the code below:

actionTaken := "05/21/2009 -- Betsy Thiede -- lskdjflksdjf
05/21/2009 -- Betsy Thiede -- sdjkflsdf jlskdfj
Betsy Thiede (05/26/2009 12:35:24 PM)
Status Changed: From 'Open' to 'On Hold
Details: sddsfsd
------------------------------------------------------
Betsy Thiede (05/26/2009 12:36:09 PM)
Status Changed: From 'On Hold' to 'Open
Details: sdfdsf
------------------------------------------------------
05/26/2009 -- Betsy Thiede -- sdfsdfs
05/26/2009 -- Betsy Thiede -- Every good boy does fine. All good things come to those who wait. For every door that closes, a window opens. My mother told me to pick the very best one and I pIpicked you
05/26/2009 -- Betsy Thiede -- 1
2
3
4
5";


aTakenExploded := @Explode(actionTaken;@NewLine);
@Prompt([OkCancelList]: [NoSort];"Selection box";"aTakenExploded";"";aTakenExploded);
temp := "";
howmany := 0;
@For(n := 1; n <= @Elements(aTakenExploded); n := n + 1;
@If(@Contains(aTakenExploded[n];" -- ");@Do(howmany := howmany + 1;temp := @Trim(temp : ("~" : aTakenExploded[n])));@Contains(aTakenExploded[n];"(");@Do(howmany := howmany + 1;@Trim(temp := temp : ("~" + aTakenExploded[n])));@Contains(aTakenExploded[n];"------------------------------------------------------"); temp; temp := temp : ("¥" + aTakenExploded[n])));
temp := @Trim(@ReplaceSubstring(@Explode(@Implode(temp);"~");"¥";""));
@Prompt([OkCancelList]:[NoSort];"Data Entry"; "temp"; "";temp)

Once I got it working, I ran an agent on the data and then exported it properly..

Monday, March 02, 2009

I shop here for pet supplies!

Discount Pet Medicine

Saturday, February 28, 2009

Found this photo! I love it..

Friday, February 27, 2009

$KeepPrivate and Replication...

I have a database where documents can have the field DOODOO = "Yes" or "No"..

If DOODOO = "Yes", I don't want them to be replicated. Users can see them on the server but I do not want the documents to replicate down to their local copy.

I tried to use a replication formula. But I had no luck. If the user puts the replication formula in themselves, it worked. But I wanted to push the replication formula out to users and I can't seem to get that work. I may be doing something wrong..most likely..

I then found the following in the Help documentation:
The Notes-generated field $KeepPrivate captures whether the current user has replicate or copy privileges for the document. This setting applies only to Notes clients.

The document in the help database that has the above information is titled Access level privileges in the ACL

So, I was all excited, thinking all I have to do is set $KeepPrivate to equal "1" and it won't replicate. Bearing in mind that the user wouldn't be able to print or copy those documents either.

But that didn't work. Documents with DOODOO = "Yes" replicated down to my local copy when I replicated.

So... since the note was on a document titled Access level privilges in the ACL... I decided to test something.

In the acl, if you uncheck the option to Replicate or Copy documents for a particular user, it prevents the user from not only replicating the database, but also prevents them from Copying or printing any documents in that entire database. Kind of like if $KeepPrivate were set on each document to equal "1".

However, on documents in a database where users have had the option of Replication or Copying documents unchecked, a $KeepPrivate field can be set to equal "0" on individual documents. Then users can print, or copy the document in the database, but still be prevented from replicating any document in the database.

Not that it helps me with my problem, but still interesting information.

I may have to have a separate database to house all the DOODOO = "Yes" field documents. And then prevent users from replicating the database at all.. Since there will only be documents in that database that have DOODOO = "Yes". But then, in order to allow the users to print the documents in the database, I will have to set the $KeepPrivate field to = 0..

Saturday, February 07, 2009

WE Surround Them

We Surround Them!
Glenn Beck is asking if you believe in 7 out of the 9 following items to send your photo to WeSourndThem@gmail.com.

1) Yes or no: Do you believe America is a good place, that we've lost our way over the years, that we have done bad things but generally speaking we tried hard. We try to make amends. We have tried to do the right thing. Just like everybody else, we fail from time to time and we have truly lost our way in the last 20 years. But gosh, if you look at America, she's good and our founders were good and our founding documents are good. We've just strayed too far away from them. Yes or no.


2) Yes or no: I believe in God. I may not go to the same church or synagogue or mosque as the majority of people in America, but I believe in God and he is the center of my life, and God does not tell people to behead others or to persecute others that see God in a different way. As long as that god is not telling them to persecute others.


Yes or no.


3) Yes or no: It is my responsibility to try to be better and a more honest person than I was yesterday. Sometimes I fail, I'll make mistakes, but it's my main mission to be better than I was personally than I was yesterday.


4) Yes or no: The family is sacred. I and my spouse are the ultimate authority under God when it comes to my family. I raise my family, and that comes with a grave responsibility. If I fail, I answer to God.


5) Yes or no: If you break the law, you pay the penalty. Justice is blind and no one is above it.


6) Yes or no: I have a right to life, liberty, and the pursuit of happiness, but that is not a guarantee of equal results.


7) Yes or no: I work hard for what I have, and I will share it with others that I choose when I choose, should I choose. Government cannot force me to be charitable.


8) It is not un-American for anyone to disagree with my opinion, but my opinion or others' opinions may be anti-American. Anti-American rhetoric would be anything that is destructive to the Constitution and our country as our founders understood it.


9) And the last one is the government works for me. The government answers to me. I do not answer to the government.

Tuesday, February 03, 2009

The Inconvenient Debt - Glenn Beck

Friday, May 16, 2008

Usability Question..

So, we were showing a Notes client application to some Requirement's gathering analysts. One of the analysts says, the users need a way to delete documents. And I say, they can. They just click the Delete key on the keyboard, or click on the delete SmartIcon, or select Delete from the Menu choices, or about 3 other ways to delete a document.

The analyst says, the user didn't know they could delete documents. It isn't "intuiative" enough.

I think, that is how users always delete documents in a Notes database.

The analyst say that the users need to have a "Delete" action button that is their face.

And also, when a user deletes a Parent document, the children should be deleted as well, in order avoid orphans.

I think, well the Standard Lotus discussion template doesn't have a Delete action button and it doesn't remove the children when a parent document is deleted. And if Lotus doesn't do it, it must be the way... I don't think any of the templates provided by Lotus have an "intuitive" delete functionality. If it is what Lotus provides, isn't that good enough?

So, I asked Nathan Freeman what he thought, and he agreed it that the way documents were deleted in Notes databases was poor UI design. Ugh, that wasn't what I wanted to hear.

Oh well, it make sense to make a more user friendly database deletion functionality.