Then this is probably best done in a custom filter.

Give everyone "read" access to the account "shared", which will trickle down to
"shared(username)".

The How-To components have example filters of how to alter user attributes and
metadata attributes. This is the place to start for the sample code.


--- In intradoc_users@yahoogroups.com, "Jason C" <jason.chandler@...> wrote:
>
> No, what I am trying to do is not a global change. There is one type of
document in our organization that each employee creates to share publicly and
only that employee has edit writes to it (plus admins). I did not mean to imply
that all documents would abide by this requirement.
>
> --- In intradoc_users@yahoogroups.com, "William Phelps" <wjphelps@> wrote:
> >
> > <snip>I want to set up our content server so that employees can share
documents that everyone has Read access to but only the employee has write
access. How would I do this?</snip>
> >
> > <snip>Does Brett's suggestion fit the requirement? Definitely an easy OOTB
solution if it does.</snip>
> >
> > <snip>I wish that would work, but Brett's suggestion would be a global
change.</snip>
> >
> > And the change for which you are asking isn't a global change? It certainly
sounds like it is, judging from the conversation thus far. I think Brett's
suggestion is spot on.
> >
> > How about some more detail?
> >
> >
> >
> > --- In intradoc_users@yahoogroups.com, "Jason C" <jason.chandler@> wrote:
> > >
> > > I wish that would work, but Brett's suggestion would be a global change.
> > >
> > > --- In intradoc_users@yahoogroups.com, Chris Owens <chris.owens@> wrote:
> > > >
> > > > Hi Jason,
> > > >
> > > > Does Brett's suggestion fit the requirement? Definitely an easy OOTB
solution if it does. More info on the setting (Allow only original contributor
to check out checkbox) here:
> > > >
> > > >
http://docs.oracle.com/cd/E21764_01/doc.1111/e10792/e01_interface.htm#CACGCEBH
> > > >
> > > > ~Chris
> > > >
> > > > --
> > > > Christopher Owens
> > > > Solution Architect
> > > >
> > > > [Description: team-informatics-logo.gif]
> > > >
> > > > TEAM Informatics, Inc.
> > > > 3900 Northwoods Drive, Suite 350 | Arden Hills, MN 55112
> > > > E chris.owens@<mailto:chris.owens@>
> > > > Corporate Office +1.651.222.TEAM (8326) D +1.715.207.0647 M
+1.651.261.1727 AUS +61.041.522.6028
> > > > www.teaminformatics.com<http://www.teaminformatics.com/>
> > > > This message may contain confidential information. If you receive this
message in error or are not
> > > > the intended recipient, you may not disseminate this message and you are
requested to erase all
> > > > copies of this message and attachments.
> > > > P Please consider the environment before printing this email.
> > > >
> > > > From: intradoc_users@yahoogroups.com
[mailto:intradoc_users@yahoogroups.com] On Behalf Of Jason C
> > > > Sent: Saturday, January 21, 2012 1:55 PM
> > > > To: intradoc_users@yahoogroups.com
> > > > Subject: [intradoc_users] Re: Limiting write access to author
> > > >
> > > >
> > > >
> > > > Bex,
> > > > I'm not having any luck inserting idoc script into the credential map.
Is that really even possible? And if not, where would I start on a custom Java
component?
> > > >
> > > > --- In
intradoc_users@yahoogroups.com<mailto:intradoc_users%40yahoogroups.com>, Brian
'Bex' Huff <bex@<mailto:bex@>> wrote:
> > > > >
> > > > >
> > > > > The 'employee ID' needs to be in an attribute in LDAP. Then you can
map it over to a user metadata field, just like 'full name' and 'email address.'
Once available, you should be able to use a credential map to grant read/write
access to the account 'shared-<$uEmployeeId$>'
> > > > >
> > > > > If that doesn't work, then you might need a custom Java component to
do the mapping.
> > > > >
> > > > > --
> > > > >
> > > > > Brian 'Bex' Huff
> > > > > Oracle ACE Director
> > > > > Chief Software Architect
> > > > > Bezzotech - THE Premier Oracle ECM Solution Provider
> > > > > Email: bex@
> > > > > Mobile: +1.612.227.6057
> > > > >
> > > > > Designing a Content Management or Enterprise 2.0 strategy? This may
help:
> > > > > http://bezzotech.com/library.html
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Jan 17, 2012, at 3:48 PM, Jason C wrote:
> > > > >
> > > > > > I want to set up our content server so that employees can share
documents that everyone has Read access to but only the employee has write
access. How would I do this?
> > > > > >
> > > > > > * Our users are externally managed in LDAP / Oid
> > > > > > * Content server 10gR3
> > > > > > * We are using accounts
> > > > > >
> > > > > > I thought about having LDAP assign everyone to an account based on
employee ID (for example "shared-[employeeID]") but our admins are concerned
that it would make LDAP unmanageable with thousands of accounts.
> > > > > >
> > > > > > Is there a way to do this with credential maps? I can't figure out
how to extract employee ID from the user profile to create assign in the map.
> > > > > >
> > > > > > Should I be looking at a different way of accomplishing this?
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>