#duraspace IRC Log


IRC Log for 2009-07-30

Timestamps are in GMT/BST.

[0:19] * krnl__ (i=krnl_@ has joined #duraspace
[0:25] * krnl_ (n=pcbetche@ Quit (Read error: 60 (Operation timed out))
[1:33] * mdiggory (n=mdiggory@sr-71.srgs01.resnet.ubc.ca) has joined #duraspace
[2:14] * mdiggory (n=mdiggory@sr-71.srgs01.resnet.ubc.ca) Quit ()
[2:25] * krnl_ (i=krnl_@ has joined #duraspace
[2:54] * krnl__ (i=krnl_@ Quit (Read error: 110 (Connection timed out))
[3:16] * bradmc (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) Quit (Read error: 104 (Connection reset by peer))
[3:26] * bradmc (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) has joined #duraspace
[6:11] * krnl__ (i=krnl_@ has joined #duraspace
[6:12] * krnl_ (i=krnl_@ Quit (Nick collision from services.)
[6:12] * krnl__ is now known as krnl_
[6:32] * bradmc_ (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) has joined #duraspace
[6:32] * bradmc (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) Quit (Read error: 104 (Connection reset by peer))
[6:40] * krnl_ (i=krnl_@ Quit (Nick collision from services.)
[6:41] * krnl_ (i=krnl_@ has joined #duraspace
[6:56] * krnl_ (i=krnl_@ Quit (Nick collision from services.)
[6:57] * krnl_ (i=krnl_@ has joined #duraspace
[7:10] * awoods (n=awoods@pool-71-191-160-185.washdc.fios.verizon.net) has joined #duraspace
[7:40] * bradmc_ (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) Quit ()
[8:15] * mhwood (i=mwood@mhw.ulib.iupui.edu) has joined #duraspace
[8:22] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[8:28] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit ()
[8:36] * ksclarke (n=kevin@ip-152010148147.library.appstate.edu) has joined #duraspace
[8:43] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[8:44] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit (Client Quit)
[9:13] * mdiggory (n=mdiggory@sr-71.srgs01.resnet.ubc.ca) has joined #duraspace
[10:01] * michaeldb (n=michaeld@CPE002436a25b34-CM000a739b087e.cpe.net.cable.rogers.com) has joined #duraspace
[10:36] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[10:59] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit ()
[11:19] * mdiggory (n=mdiggory@sr-71.srgs01.resnet.ubc.ca) Quit ()
[11:30] * cwilper (n=cwilper@74-44-156-57.dsl1-erie.roch.ny.frontiernet.net) Quit (Remote closed the connection)
[11:31] * cwilper (n=cwilper@74-44-156-57.dsl1-erie.roch.ny.frontiernet.net) has joined #duraspace
[11:49] <cbeer> cwilper: is there any good way to debug xacml policies?
[11:55] <cwilper> cbeer: for validity, there's the validate-policy script, but for testing the actual behavior, the best way i know of is trial and error. if it's a repository-wide policy, it's useful to use the fedora-reload-policies script so you don't have to restart fedora. if it's object-specific (a POLICY datastream), making repeated mods to it and testing the results manually is the only way i know of.
[11:56] <cbeer> ok; would be nice if there was a way to inspect some of those attribute values or log the evaluation process or similar
[11:59] <cwilper> well, there is some logging possible, but the messages are rather cryptic to me...may be helpful to you. you can get a lot of log messages by editing config/log4j.properties and restarting fedora.
[12:00] <cbeer> hm; maybe i'll tinker with that later
[12:01] <cwilper> looking at it now, i see that the AttributeFinder logging config is commented out; uncommenting it may help. also setting the log level to debug on fedora.server.security should get you lots of log messages.
[12:01] <cbeer> cool, thanks
[12:02] <cbeer> now i just need to figure out why my activemq listener only processes the first message..
[12:03] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[12:03] <cwilper> hrmm, haven't heard of that, good luck
[12:05] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit (Client Quit)
[12:29] * rhcl (n=rhcl@ has joined #duraspace
[12:51] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[12:53] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit (Client Quit)
[13:38] <cbeer> it must have been ruby punishing me for crimes against proper architecture
[14:16] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[14:20] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit (Client Quit)
[15:01] * bradmc (n=bradmc@c1-fw.constantcontact.com) has joined #duraspace
[15:02] * bradmc (n=bradmc@c1-fw.constantcontact.com) Quit (Client Quit)
[15:40] <rhcl> Do people ever talk here? Ask questions?
[15:41] <mhwood> You just did!
[15:41] <rhcl> Life!
[15:42] <rhcl> OK, here goes. Besides providing a unique identifier for a digital item, what controls or other information does a digital handle identifier provide for an object in dspace?
[15:43] <mhwood> Oh, good, one I maybe can't answer. I'm not aware of anything else, but if I'm wrong perhaps we'll both be enlightened.
[15:44] <mhwood> What else should it do?
[15:44] <rhcl> This line from the handle page prompted my question:
[15:44] <rhcl> Digital Object Architecture provides a means of managing digital information in a network environment. A digital object has a machine and platform independent structure that allows it to be identified, accessed and protected, as appropriate.
[15:45] <mhwood> It sounds as though the Handle System is but a part of this Digital Object Architecture.
[15:46] <rhcl> Yea, and immediately after the DOA is the part on HDL
[15:46] <rhcl> The Handle System is a general purpose distributed information system that provides efficient, extensible, and secure HDL identifier and resolution services for use on networks such as the Internet. It includes an open set of protocols, a namespace, and a reference implementation of the protocols.
[15:46] <rhcl> That kinda made it sound like there was more to it than a unique identifier.
[15:48] <mhwood> AFAIK the Handle System itself only supplies a persistent opaque identifier that can be mapped (and re-mapped) to digital objects. Actual interchange is out-of-scope for Handles, if I'm not mistaken.
[15:49] <mhwood> Object interchange that is. Handles can be passed around -- that's the reason for them.
[15:50] <mhwood> http://www.cnri.reston.va.us/activities.html
[15:51] <mhwood> CNRI has a number of projects going. DOA and Handle are two of them.
[15:55] <rhcl> So the handle system is databasing all these identifiers? Is it storing only the IDs, or is is pulling item (meta)data when an ID is requested?
[15:56] <mhwood> Less than that. The root resolver only keeps track of which local resolvers map to which prefixes, and bounces queries to those local resolvers.
[15:59] <mhwood> Handle is all about naming things. The system does nothing except map Handle references to referrals. And most of the work is done by the local resolvers.
[16:00] <rhcl> OK, I think I have a better understanding of it now.
[16:01] <rhcl> I guess you must work with DSpace and digital archives some?
[16:02] <mhwood> Yes, some. I'm a programmer and sysadmin. If scholarworks.iupui.edu is down, for example, it's my fault. :-/
[16:03] <rhcl> Yea, I'm a sysadmin here too, dabbling in a digital archive project.
[16:08] <mhwood> Welcome to the DSpace community. It's often quiet in here, but a number of folk are usually lurking and you may find an answer. Otherwise try the mailing lists.
[16:10] <rhcl> TNX
[16:32] * mhwood (i=mwood@mhw.ulib.iupui.edu) has left #duraspace
[16:40] * cwilper (n=cwilper@74-44-156-57.dsl1-erie.roch.ny.frontiernet.net) Quit (Read error: 110 (Connection timed out))
[16:57] * bradmc (n=bradmc@207-172-69-79.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com) has joined #duraspace
[17:26] * ksclarke (n=kevin@ip-152010148147.library.appstate.edu) has left #duraspace
[17:43] * cbeer_ (n=chris@dsl092-069-087.bos1.dsl.speakeasy.net) has joined #duraspace
[18:11] * rhcl (n=rhcl@ has left #duraspace
[18:45] * ksclarke (n=kevin@adsl-235-102-10.clt.bellsouth.net) has joined #duraspace
[18:45] * ksclarke (n=kevin@adsl-235-102-10.clt.bellsouth.net) has left #duraspace
[18:47] * michaeldb (n=michaeld@CPE002436a25b34-CM000a739b087e.cpe.net.cable.rogers.com) Quit ("Leaving...")

These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.