[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#613553: marked as done (document school workflow with gosa)



Your message dated Sat, 16 Oct 2021 13:44:08 +0200
with message-id <YWq7CNJjelyWOwQv@star>
and subject line fixed
has caused the Debian Bug report #613553,
regarding document school workflow with gosa
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
613553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613553
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
package: debian-edu-doc
severity: wishlist
x-debbug-cc: debian-edu@lists.debian.org

Hi,

On Montag, 14. Februar 2011, José L. Redrejo Rodríguez wrote:
>> Or you can tell the CipUX Team (for example on cipux-devel ore here
>> ) what you need, and we will see if we can provide it.
> Massive importation of user accounts in September, aplying permissions
> and groups , using information provided by some xml and zip files
> exported from the regional educative administration tool. The xml files
> include the user login, classroom or department if they're a teacher and
> student photos to be added to ldap.
>
> At the same time the accounts are created, cleaning of old accounts and
> moving existing ones keeping their uid and gids is needed (as an
> example, jmartinez user moves from 1A to 2B in september).
>
> I can provide xml and zip files as they are generated from the
> administration tool. A xml file is generated with the teachers of every
> school, and a zip cotaining photos and another xml with the students.
>
> So, it's a very specific need, depending tightly on the official
> administrative tool used by our government.

while the details of this are specific, the general workflow is not and 
something like this should be documented (at least) for our default admin 
tool, which atm is gosa. 

Filing this in the BTS so that it doesn't get forgotten. 


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
Related information has been added a long time ago (iirc for the squeeze 
manual), closing this bug now.

Wolfgang

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: