> I'll take care of it… do you have an ID of at least one of the docs?  I have a feeling prod is suffering from a misconfiguration as well..  I'll fix it at the same time.

> - Jim

> Jim Klo
> Senior Software Engineer
> Center for Software Engineering
> SRI International
> t. @nsomnac

> On Oct 10, 2012, at 12:44 AM, joe hobson <joehob...@gmail.com>
>  wrote:

>> Yesterday I noticed that some of the paradata records being published to LR node01 by Brokers of Expertise were showing up with submitter of j...@navigationnorth.com, rather than Brokers of Expertise (example: http://goo.gl/2BEFQ). We haven't changed how Brokers publishes, other than setting up a Persona account and going through the steps on the node. I'm almost positive I did the same steps on sandbox as I did on node01, yet my records are correct on sandbox (signed by the Brokers app, not the node) and not on node01. I tried to compare the 2 oauth-key setups for my account but this page does not load: http://sandbox.learningregistry.org/apps/oauth-key-management

>> I don't want node01 signing on my behalf, but I can't see how to revoke the setup for my account so that the node won't keep signing my records. There are now records in the LR published by Brokers that appear to be submitted by j...@navigationnorth.com. This would be okay except for the fact that I just published about 1000 resources from National Museum of American History and they were supposed to be signed by Smithsonian (key was provided). As far as I know, I did the exact same setup and publish mechanisms on sandbox and node01, yet the node01 records are signed by the node and not Smithsonian. Anyone care to delete more records from LR?

>> any help is greatly appreciated. thanks. ... .joe

>> --