• Replies 6 replies
  • Subscribers 209 subscribers
  • Views 70 views
  • Users 0 members are here
Related

student data in v12 orders

Ellie McKay
$organization

Hey all -  We are on the cusp of moving into v12 and I am curious about where people are storing student information in v12 orders.  For classes we currently collect the student name through Special Request (SR) and use the SR Category to capture the student's grade and the SR Notes to comment on any class specific information (ex. will be late on Monday, place with Sally Sue, etc).  With v12, we are not able to capture those details on the subline level, only the student's name as the recipient.  The only solutions I have right now are to 1.still make each line item unique to the student and collect the grade as an expiring attribute or 2. making everything an attribute, but the nature of student information is so dynamic that I would rather not make it intrinsic to the student's constituent record.  Anyone have any thoughts?

  • $organization

    Hi Ellie,

    We're still on v11, but we're using a mix of those approaches now. We use the special request on the lineitem to store a customer number for the student. That means we have to enforce a 1 lineitem per student rule. Since we can't adjust the dropdown on a per performance basis (we're TNEW users - I see you are as well), we put messaging on each performance page asking the user to only reserve one spot at a time. We also put in place a customization that will check for education classes with more than one seat, and remove any extras before the user lands on the cart page. The information submitted with the remaining seat still goes through. 

    As for the information we store on the child's account, we have a custom tab and some attributes, though it may be just as easy to use all attributes. 

    We use the procedure LRP_TN_EXPRESS_WEB_SAVE_AUX_DATA so we can remit data to attributes (like birthday), research (like health/allergy info), names (aliases) etc. 

    I'm eager to get to V12 and see what options we have for working with recipient/initiator/owner. I'd really love to get rid of that hacky "only reserve one ticket please" business.

  • $organization in reply to Brian Graham

    Ah, but that is the issue.  We are playing with v12 in TEST and while you can identify the recipient on the subline level (great for that parent signing 3 kids up for the same class), as far as I can tell that is the only information you can store there so if you wanted to make any notes about the individual recipient, there is not a place to do so in the order.  

  • $organization

    I don’t have a version 12 up and running right now.

     

    However, I wonder about making the grade level or maybe better the age notations over on the child’s account.  Not on the actual order.

     

    This would make reporting harder.  However, data entry would be straight forward once the child account is setup.

     

    Just a thought…

     

    --Tom

    …

    718.724.8135

    tbrown@BAM.org

     

    From: Tessitura Education Forum [mailto:forums-education@tessituranetwork.com] On Behalf Of Ellie McKay
    Sent: Wednesday, February 12, 2014 10:36 AM
    To: Thomas Brown
    Subject: Re: [Tessitura Education Forum] student data in v12 orders

     

    Ah, but that is the issue.  We are playing with v12 in TEST and while you can identify the recipient on the subline level (great for that parent signing 3 kids up for the same class), as far as I can tell that is the only information you can store there so if you wanted to make any notes about the individual recipient, there is not a place to do so in the order.  

    From: Brian Graham <bounce-briangraham8283@tessituranetwork.com>
    Sent: 2/11/2014 9:04:35 AM

    Hi Ellie,

    We're still on v11, but we're using a mix of those approaches now. We use the special request on the lineitem to store a customer number for the student. That means we have to enforce a 1 lineitem per student rule. Since we can't adjust the dropdown on a per performance basis (we're TNEW users - I see you are as well), we put messaging on each performance page asking the user to only reserve one spot at a time. We also put in place a customization that will check for education classes with more than one seat, and remove any extras before the user lands on the cart page. The information submitted with the remaining seat still goes through. 

    As for the information we store on the child's account, we have a custom tab and some attributes, though it may be just as easy to use all attributes. 

    We use the procedure LRP_TN_EXPRESS_WEB_SAVE_AUX_DATA so we can remit data to attributes (like birthday), research (like health/allergy info), names (aliases) etc. 

    I'm eager to get to V12 and see what options we have for working with recipient/initiator/owner. I'd really love to get rid of that hacky "only reserve one ticket please" business.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Education Forum. You may reply to this message to post to the Education forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization in reply to Tom Brown (Past Member)

    We do enter the DOB as an attribute on the student's account, but all of our classes are by current grade and we've been tracking that in the order.  Maybe we can figure out a way to create an auto-updating attribute that will update the grade each year.  Hmmm.

  • $organization in reply to Ellie McKay

    Something that I saw someone do once is have a price type reason attached to any prices used for classes and have that reason be a grade. So you'd pick something like 'Full Price Student' and then pick Grade 5 for the reason. Not sure if that would work for you, but it is something you could do per sublineitem.

    - Heather

  • $organization

    Creating an estimate grade level based on age would not be too hard.

     

    This would use the Getdate() and data arithmetic.

     

    6 Year Olds here in the Us are in 1st grade

    7 Year Olds are in 2nd Grade…

    …

     

    You could get more sophisticated with date cut offs if they are consistent in your area.

     

    If you need more accuracy this would not work.

     

    --Tom

    …

    718.724.8135

    tbrown@BAM.org

     

    From: Tessitura Education Forum [mailto:forums-education@tessituranetwork.com] On Behalf Of Ellie McKay
    Sent: Wednesday, February 12, 2014 12:02 PM
    To: Thomas Brown
    Subject: RE: [Tessitura Education Forum] student data in v12 orders

     

    We do enter the DOB as an attribute on the student's account, but all of our classes are by current grade and we've been tracking that in the order.  Maybe we can figure out a way to create an auto-updating attribute that will update the grade each year.  Hmmm.

    From: Tom Brown <bounce-tombrown3568@tessituranetwork.com>
    Sent: 2/12/2014 10:36:25 AM

    I don’t have a version 12 up and running right now.

     

    However, I wonder about making the grade level or maybe better the age notations over on the child’s account.  Not on the actual order.

     

    This would make reporting harder.  However, data entry would be straight forward once the child account is setup.

     

    Just a thought…

     

    --Tom

    …

    718.724.8135

    tbrown@BAM.org

     

    From: Tessitura Education Forum [mailto:forums-education@tessituranetwork.com] On Behalf Of Ellie McKay
    Sent: Wednesday, February 12, 2014 10:36 AM
    To: Thomas Brown
    Subject: Re: [Tessitura Education Forum] student data in v12 orders

     

    Ah, but that is the issue.  We are playing with v12 in TEST and while you can identify the recipient on the subline level (great for that parent signing 3 kids up for the same class), as far as I can tell that is the only information you can store there so if you wanted to make any notes about the individual recipient, there is not a place to do so in the order.  

    From: Brian Graham <bounce-briangraham8283@tessituranetwork.com>
    Sent: 2/11/2014 9:04:35 AM

    Hi Ellie,

    We're still on v11, but we're using a mix of those approaches now. We use the special request on the lineitem to store a customer number for the student. That means we have to enforce a 1 lineitem per student rule. Since we can't adjust the dropdown on a per performance basis (we're TNEW users - I see you are as well), we put messaging on each performance page asking the user to only reserve one spot at a time. We also put in place a customization that will check for education classes with more than one seat, and remove any extras before the user lands on the cart page. The information submitted with the remaining seat still goes through. 

    As for the information we store on the child's account, we have a custom tab and some attributes, though it may be just as easy to use all attributes. 

    We use the procedure LRP_TN_EXPRESS_WEB_SAVE_AUX_DATA so we can remit data to attributes (like birthday), research (like health/allergy info), names (aliases) etc. 

    I'm eager to get to V12 and see what options we have for working with recipient/initiator/owner. I'd really love to get rid of that hacky "only reserve one ticket please" business.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Education Forum. You may reply to this message to post to the Education forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Education Forum. You may reply to this message to post to the Education forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!