Re: [Tiki-devel] Profiles: personal/user profiles or externalrepositories?

[<ge...@en...>]

Torsten - why don't you just set up your own profiles site? You can then do
what you like completely privately.
 
cheers
 
geoff
 
  _____  

From: Torsten Fabricius [mailto:to...@fa...] 
Sent: 02 November 2011 11:25
To: Tiki Devlist
Subject: [Tiki-devel] Profiles: personal/user profiles or
externalrepositories?


Hi Devs,

since a while now I am thinking about how to use the Profiles to ease my
daily life.

So I did learn now how to make my own profile by exporting from a custom
configuration based on a clean installation.
-> just a few minutes to understand that.

For now I see the only way to use the exported data in publishing the data
on the profiles.t.o site (same as if I would edit this from scratch by
myself).

Once I want to setup a profile to provide the community with a certain
configuration I find this app-store-like approach quite superfantastic.

But when I need s.th like a personalised profile included my contact
details, certain specific pages or customers details, I do not want to
publish this on a public site.
Further more I do not want to "pollute" the "profiles-store" with masses of
personal profiles, which might be just similar to each other and not real
any use to other community members.

So how can I use the YAML data to "import" my own personal profiles without
needing to publish on profiles.t.o?

Should I use "Datachannels" for this - and if yes, how?

Or should we extend the Admin -> Profiles to the possibility to add
"external repositories", so s.b. could set up his/her own small profiles
site, with specific profiles for collegues or customers?
Could this be done with Datas (YAML on Wikipages) that are only visible if
logged in to the repository? I mean kind of a non-public repository.

Another possibly useful approach:
An extra type category "User profile" on profiles.t.o, where I could setup
personal profiles without "polluting" the rest?

Idea would be just the username as prefix of the YAML-page name and
categorize with "User profile" instead of "Full profile", "Learning profile"
etc.
This profile still could be visible for everybody, but not polluting the
main profiles, as it could be filtered.
Then I'd have to add specific personal data "manually" - as I would not
include that in the profile, but ...

* I still could save much time for similar new installations
* I could play around with these specific personal profiles without
upsetting anybody else who frequently uses the mainprofiles like WYSIWYG_6x
* I could include custom themes (for ex. for a customer) in such a profile
-> install a plain Tiki -> upload the custom files -> THEN apply the
personal profile -> done

What do you think about my idea?

Cheers
Torsten



  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1834 / Virus Database: 2092/4590 - Release Date: 11/01/11

  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1834 / Virus Database: 2092/4590 - Release Date: 11/01/11