Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » Human Requestor not included in XDS.a Doc Consumer Audit Record
Human Requestor not included in XDS.a Doc Consumer Audit Record [message #40584] Fri, 25 January 2008 01:47 Go to next message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
At comming Connectathon there will be some requirements for XDS syslog as
described at
http://ihewiki.wustl.edu/wiki/index.php/XDS_Syslog_testing_r equirements#ITI-17__.28Retrieve.29__Document_Consumer
and I noticed it's saying Human Requestor block must be included in Doc
Consumer Audit Record for every transaction involved. First I thought
it's optional because of "(0..1)" descriptor (please see ITI TF-2
3.16.4.1.5) but Bill told me "The Document Consumer end of a Retrieve
Document transaction has the opportunity to know the human requestor. If
it is known it needs to be logged." - that sounds reasonable. So I
checked audit records generated by the Bridge and found there's no third
ActiveParticipant. There're just two of them, Source and Destination.

As long as I see all parameters given to the Bridge is filled correctly.
Is there any configuration file to be modified to put Human Requestor in
audit records, or is it just something to be fixed in the connectathon
week?

Anyway I really appreciate every your help and continuous efforts, and
wish you all success at the connectathon.

Thanks,
Takeo Satomi
Re: Human Requestor not included in XDS.a Doc Consumer Audit Record [message #40617 is a reply to message #40584] Fri, 25 January 2008 13:08 Go to previous message
Matthew Davis
Messages: 269
Registered: July 2009
Senior Member
Hi Takeo,

This is kind of bothersome to me. We decided a couple months ago *NOT*
to include the Human Requestor "ActiveParticipant" block, for a couple
reasons (can't recall the reasons exactly). I'll take a look at the
spec again and try to figure out what will be needed to populate this
item. We won't implement it before Connectathon, but if Bill M demands
that it be there, we'll deal with it then.

Thanks for letting me know that it may be expected. We had sort of
discounted it as not being necessary in our scope.

-Matt



Takeo Satomi wrote:
> At comming Connectathon there will be some requirements for XDS syslog
> as described at
> http://ihewiki.wustl.edu/wiki/index.php/XDS_Syslog_testing_r equirements#ITI-17__.28Retrieve.29__Document_Consumer
>
> and I noticed it's saying Human Requestor block must be included in Doc
> Consumer Audit Record for every transaction involved. First I thought
> it's optional because of "(0..1)" descriptor (please see ITI TF-2
> 3.16.4.1.5) but Bill told me "The Document Consumer end of a Retrieve
> Document transaction has the opportunity to know the human requestor.
> If it is known it needs to be logged." - that sounds reasonable. So I
> checked audit records generated by the Bridge and found there's no third
> ActiveParticipant. There're just two of them, Source and Destination.
>
> As long as I see all parameters given to the Bridge is filled
> correctly. Is there any configuration file to be modified to put Human
> Requestor in audit records, or is it just something to be fixed in the
> connectathon week?
>
> Anyway I really appreciate every your help and continuous efforts, and
> wish you all success at the connectathon.
>
> Thanks,
> Takeo Satomi
>
Re: Human Requestor not included in XDS.a Doc Consumer Audit Record [message #584545 is a reply to message #40584] Fri, 25 January 2008 13:08 Go to previous message
Matthew Davis
Messages: 269
Registered: July 2009
Senior Member
Hi Takeo,

This is kind of bothersome to me. We decided a couple months ago *NOT*
to include the Human Requestor "ActiveParticipant" block, for a couple
reasons (can't recall the reasons exactly). I'll take a look at the
spec again and try to figure out what will be needed to populate this
item. We won't implement it before Connectathon, but if Bill M demands
that it be there, we'll deal with it then.

Thanks for letting me know that it may be expected. We had sort of
discounted it as not being necessary in our scope.

-Matt



Takeo Satomi wrote:
> At comming Connectathon there will be some requirements for XDS syslog
> as described at
> http://ihewiki.wustl.edu/wiki/index.php/XDS_Syslog_testing_r equirements#ITI-17__.28Retrieve.29__Document_Consumer
>
> and I noticed it's saying Human Requestor block must be included in Doc
> Consumer Audit Record for every transaction involved. First I thought
> it's optional because of "(0..1)" descriptor (please see ITI TF-2
> 3.16.4.1.5) but Bill told me "The Document Consumer end of a Retrieve
> Document transaction has the opportunity to know the human requestor.
> If it is known it needs to be logged." - that sounds reasonable. So I
> checked audit records generated by the Bridge and found there's no third
> ActiveParticipant. There're just two of them, Source and Destination.
>
> As long as I see all parameters given to the Bridge is filled
> correctly. Is there any configuration file to be modified to put Human
> Requestor in audit records, or is it just something to be fixed in the
> connectathon week?
>
> Anyway I really appreciate every your help and continuous efforts, and
> wish you all success at the connectathon.
>
> Thanks,
> Takeo Satomi
>
Previous Topic:Human Requestor not included in XDS.a Doc Consumer Audit Record
Next Topic:PDQ limit
Goto Forum:
  


Current Time: Thu Aug 28 03:22:27 EDT 2014

Powered by FUDForum. Page generated in 0.01615 seconds