SDSHOWTO:Merging people - Revision history

Sinan.soykut: /* Online app move account to another person */

2016-01-18T22:02:05Z

Online app move account to another person

Sinan.soykut: /* Online app account and parent */

2015-11-30T21:22:25Z

Online app account and parent

Sinan.soykut: /* Online app account and parent */

2015-11-16T21:48:24Z

Online app account and parent

← Older revision		Revision as of 14:48, 16 November 2015
Line 64:		Line 64:
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.		* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.
	*Navigate to Admin Menu > System Data > Memcache Maintenance, and remove keys for any for all the records you changed. If for some reason you are unable to do this, you'll have to flush the entire SDS Cache.		*Navigate to Admin Menu > System Data > Memcache Maintenance, and remove keys for any for all the records you changed. If for some reason you are unable to do this, you'll have to flush the entire SDS Cache. That can be done with the following steps:
	<pre>		<pre>
	open PuTTY and SSH to sds1.smus.ca		open PuTTY and SSH to sds1.smus.ca

Sinan.soykut: /* Online app account and parent */

2015-11-16T21:46:38Z

Online app account and parent

← Older revision		Revision as of 14:46, 16 November 2015
Line 63:		Line 63:
	* Back in the sidebar, filter by person and click into the person table		* Back in the sidebar, filter by person and click into the person table
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.		* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.
	* ~~Run~~ PuTTY and SSH to sds1.smus.ca		*Navigate to Admin Menu > System Data > Memcache Maintenance, and remove keys for any for all the records you changed. If for some reason you are unable to do this, you'll have to flush the entire SDS Cache.
	* Run the following commands at the command prompt		<pre>
			open PuTTY and SSH to sds1.smus.ca
			Run the following commands at the command prompt

	~~<pre>~~
	telnet memcache.smus.ca 11211		telnet memcache.smus.ca 11211
	flush_all		flush_all

Chris.kloosterman at 20:51, 19 September 2013

2013-09-19T20:51:24Z

← Older revision		Revision as of 13:51, 19 September 2013
Line 1:		Line 1:
	This depends on who you are merging:		This depends on who you are merging:

			== Online app move account to another person ==

			Usually this happens if the parent signs up for an online application account as the student and admissions catches it. This is the easiest one to fix as it has the fewest complications.

			* Determine the person_id of the student and the person_id of the parent (search for the names, hover over the name, and get the person_id from the destination URL)
			* You should now have two person_ids: student account and parent account
			* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...
			* In the sidebar, go to SDS -> Tables
			* Filter by app_app, then click into the app_application table
			* Click search in the top bar, and search for person_id of the student account
			* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go
			* Back in the sidebar, filter by theatre_rec and click into the theatre_receipt table
			* Click search in the top bar, and search for person_id of the student account
			* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go
			* Back in the sidebar, filter by person_ses and click into the person_session table
			* Click search in the top bar, and search for person_id of the student account
			* Assuming a record comes up, delete the record
			* Back in the sidebar, filter by person and click into the person table
			* Click search in the top bar, and search for person_id of the student account
			* Scroll right and make note of the username. You need to delete this using Apache Directory Studio later.
			* Delete the record
			* Run Apache Directory Studio (setup instructions below) and connect to LDAP1
			** Right click o=smus.bc.ca. and choose Quick Search
			** For Search Base, enter o=smus.bc.ca.
			** For filter, enter (uid=user.name)
			** Click OK
			** Assuming a search result appears, click into it
			** Right click the search result in the sidebar and choose Delete Entry
			** Close Apache Directory Studio
			* Run PuTTY and SSH to sds1.smus.ca
			* Run the following commands at the command prompt

			<pre>
			telnet memcache.smus.ca 11211
			flush_all
			quit
			exit
			</pre>

			Note: this flushes the SDS cache, so SDS performance will be slower for a while after this command is run

	== Online app account and parent ==		== Online app account and parent ==

Chris.kloosterman at 20:45, 19 September 2013

2013-09-19T20:45:01Z

← Older revision		Revision as of 13:45, 19 September 2013
Line 62:		Line 62:
	* Assuming a record comes up, scroll across and make note of the username		* Assuming a record comes up, scroll across and make note of the username
	* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, but you need to decide whether to link to the actual student person_id or the target parent person_id. Most additional data will need to be relinked to the actual student person_id. Some data is better off just being deleted, like duplicate admissions records or duplicate person_log entries (eg: if there is an enquiry and an imported application).		* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, but you need to decide whether to link to the actual student person_id or the target parent person_id. Most additional data will need to be relinked to the actual student person_id. Some data is better off just being deleted, like duplicate admissions records or duplicate person_log entries (eg: if there is an enquiry and an imported application).
	* Run Apache Directory Studio and connect to LDAP1		* Run Apache Directory Studio (setup instructions below) and connect to LDAP1
	** Right click o=smus.bc.ca. and choose Quick Search		** Right click o=smus.bc.ca. and choose Quick Search
	** For Search Base, enter o=smus.bc.ca.		** For Search Base, enter o=smus.bc.ca.

Chris.kloosterman at 20:44, 19 September 2013

2013-09-19T20:44:39Z

← Older revision		Revision as of 13:44, 19 September 2013
Line 81:		Line 81:

	Note: this flushes the SDS cache, so SDS performance will be slower for a while after this command is run		Note: this flushes the SDS cache, so SDS performance will be slower for a while after this command is run

			== Apache Directory Studio ==

			If you need Apache Directory Studio, download it from here: http://archive.apache.org/dist/directory/studio/stable/1.5.3.v20100330/

			Run Apache Directory Studio, then create a new connection to LDAP1:

			* In the connections box, right click in the empty space and click New Connection
			* Connection name: LDAP1, hostname: ldap1.smus.ca, port: 389, encryption: no encryption, then click Next
			* Authentication method: simple authentication, Bind DN: cn=manager,o=smus.bc.ca., Password: st..., then click Next until the end of the wizard

Chris.kloosterman at 20:38, 19 September 2013

2013-09-19T20:38:08Z

← Older revision		Revision as of 13:38, 19 September 2013
Line 3:		Line 3:
	== Online app account and parent ==		== Online app account and parent ==

			Usually this happens if the parent submitted an online application but the names didn't match and admissions didn't fix it before importing the application.

			* Determine the person_id of the duplicate parent (the online app account) real parent in SDS with a student attached (search for the name, click on the name to go into edit_parents for the real parent, hover over the link to the name. Capture the person_id of the duplicate parent and the real parent).
			* You should now have two person_ids: duplicate parent, real parent
			* Edit the duplicate parent's person record and make note of the username. Remove the username from their profile and save.
			* Edit the real parent's person record and paste the username into their record. Save the person after adding the username.
			* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...
			* In the sidebar, go to SDS -> Tables
			* Filter by app_app, then click into the app_application table
			* Click search in the top bar, and search for person_id of the duplicate parent
			* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go
			* Back in the sidebar, filter by theatre_rec and click into the theatre_receipt table
			* Click search in the top bar, and search for person_id of the duplicate parent
			* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go
			* Back in the sidebar, filter by person_ses and click into the person_session table
			* Click search in the top bar, and search for person_id of the duplicate parent
			* Assuming a record comes up, delete the record
			* Back in the sidebar, filter by person and click into the person table
			* Click search in the top bar, and search for person_id of the duplicate parent
			* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.
			* Run PuTTY and SSH to sds1.smus.ca
			* Run the following commands at the command prompt

			<pre>
			telnet memcache.smus.ca 11211
			flush_all
			quit
			exit
			</pre>

			Note: this flushes the SDS cache, so SDS performance will be slower for a while after this command is run

	== Duplicate students ==		== Duplicate students ==

Chris.kloosterman: /* Duplicate students */

2013-09-19T20:30:38Z

Duplicate students

← Older revision		Revision as of 13:30, 19 September 2013
Line 31:		Line 31:
	* Click search in the top bar, and search for person_id of the duplicate student		* Click search in the top bar, and search for person_id of the duplicate student
	* Assuming a record comes up, scroll across and make note of the username		* Assuming a record comes up, scroll across and make note of the username
	* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, but you need to decide whether to link to the actual student person_id or the target parent person_id. Most additional data will need to be relinked to the actual student person_id.		* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, but you need to decide whether to link to the actual student person_id or the target parent person_id. Most additional data will need to be relinked to the actual student person_id. Some data is better off just being deleted, like duplicate admissions records or duplicate person_log entries (eg: if there is an enquiry and an imported application).
	* Run Apache Directory Studio and connect to LDAP1		* Run Apache Directory Studio and connect to LDAP1
	** Right click o=smus.bc.ca. and choose Quick Search		** Right click o=smus.bc.ca. and choose Quick Search

Chris.kloosterman: /* Duplicate students */

2013-09-19T20:26:52Z

Duplicate students

@@ Line 32: / Line 32: @@
 * Assuming a record comes up, scroll across and make note of the username
 * Delete the record if possible.  If it is not possible, you need to look at the error message and figure out what it means.  Usually there are records in other tables pointing to this person_id that you need to look at.  Most records can be found in the same way as described above, but you need to decide whether to link to the actual student person_id or the target parent person_id.  Most additional data will need to be relinked to the actual student person_id.
+* Run Apache Directory Studio and connect to LDAP1

← Older revision		Revision as of 15:02, 18 January 2016
Line 9:		Line 9:
	* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...		* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...
	* In the sidebar, go to SDS -> Tables		* In the sidebar, go to SDS -> Tables
	* Filter by app_app, then click into the app_application table		* Filter by app_app, then click into the '''app_application''' table
	* Click search in the top bar, and search for person_id of the student account		* Click search in the top bar, and search for person_id of the student account
	* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go		* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go
	* Back in the sidebar, filter by theatre_rec and click into the theatre_receipt table		* Back in the sidebar, filter by theatre_rec and click into the '''theatre_receipt''' table
	* Click search in the top bar, and search for person_id of the student account		* Click search in the top bar, and search for person_id of the student account
	* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go		* Assuming a record comes up, click the Edit link and change the person_id to the parent account, then click Go
	* Back in the sidebar, filter by person_ses and click into the person_session table		* Back in the sidebar, filter by person_ses and click into the '''person_session''' table
	* Click search in the top bar, and search for person_id of the student account		* Click search in the top bar, and search for person_id of the student account
	* Assuming a record comes up, delete the record		* Assuming a record comes up, delete the record
	* Back in the sidebar, filter by person and click into the person table		* Back in the sidebar, filter by person and click into the '''person''' table
	* Click search in the top bar, and search for person_id of the student account		* Click search in the top bar, and search for person_id of the student account
	* Scroll right and make note of the username. You need to delete this using Apache Directory Studio later.		* Scroll right and make note of the username. You need to delete this using Apache Directory Studio later.

← Older revision		Revision as of 14:22, 30 November 2015
Line 52:		Line 52:
	* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...		* Sign into [https://sdsdev.smus.ca/phpMyAdmin phpMyAdmin] as root/st...
	* In the sidebar, go to SDS -> Tables		* In the sidebar, go to SDS -> Tables
	* Filter by app_app, then click into the app_application table		* Filter by app_app, then click into the '''app_application''' table
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go		* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go
	* Back in the sidebar, filter by theatre_rec and click into the theatre_receipt table		* Back in the sidebar, filter by theatre_rec and click into the '''theatre_receipt''' table
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go		* Assuming a record comes up, click the Edit link and change the person_id to the real parent, then click Go
	* Back in the sidebar, filter by person_ses and click into the person_session table		* Back in the sidebar, filter by person_ses and click into the '''person_session''' table
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Assuming a record comes up, delete the record		* Assuming a record comes up, delete the record
	* Back in the sidebar, filter by person and click into the person table		* Back in the sidebar, filter by person and click into the '''person''' table
	* Click search in the top bar, and search for person_id of the duplicate parent		* Click search in the top bar, and search for person_id of the duplicate parent
	* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.		* Delete the record if possible. If it is not possible, you need to look at the error message and figure out what it means. Usually there are records in other tables pointing to this person_id that you need to look at. Most records can be found in the same way as described above, and generally they can just be deleted.