Ability for parents to upload observations to two settings

[Mother_Goose]

My son attends two settings and I like to upload my own obs of things we've done at home etc. It's really frustrating having to do this twice over. Are there any plans underway to allow parents the ability to upload to both settings at the same time (if they wish)?

[FSFRebecca]

Good afternoon Mother_Goose,

Generally when a child attends two settings there is only one journal and so the parent uploads to a single journal but both settings can see it.

 

I've put some options for the settings to consider below:

For safeguarding, each Tapestry account has its own database for security reasons. This means that settings cannot share a child’s profile as it cannot exist simultaneously in two Tapestry accounts, with changes being made by one setting appearing in the profile owned by the second setting. However, there are a couple of options of how you can proceed.

Option 1: Staff at setting 1 could be added to the profile on setting 2 as relatives. Both settings would then be able to comment on the same journal and would be able to see what they have each added (provided all posts are published). The drawback here is that assessments on observations can only be seen by relatives if the setting has set their account up so that all parents can view all of a particular framework’s assessments. It is not possible to select which relatives can see assessment details and which cannot. They would also not be able to access the snapshots/analysis sections regardless of the permissions you have set. In addition to this, relatives cannot add assessments to observations so only the second setting could only make observation with media and notes.

Option 2: Staff at one setting could be added to the other package as staff members. In this case, both would have full access to that child's data. To do this without creating any safeguarding issues you would need consider whether the package the other setting is added to only allows staff to see their key children. If so, then they just need to add the member of staff for the other setting and attach the child as a key child. If the package the other is added to allows staff to see all children though, or children other than their key children, they can proceed as follows:

All children that a staff member in the first setting might want to observe are set as key children, this could possibly be all children.

They then set all staff to be able to see only their key children.

Then they can set up manual groups for key children, called 'X's' key children, then they will be able to use the groups filter to look at different things for analysis purposes.

The member of staff for the second setting can then be added as a staff member and assigned the shared child as a key child.

One of the main drawbacks to option 2 is that the analysis data will be limited for the setting set up as a staff member on the other package. This means they will still need to compare attainment/progress data manually with the cohort in their own setting.

Furthermore, if the child is in group photos the second setting key person will see the other children in the photos. You would need to think about whether this is a problem and if you can get permission for this or a way to work around it.

Hope those might help?

[Mother_Goose]

Thanks for the reply Rebecca. Unfortunately, those two options you suggested are not viable work arounds, so there are two separate journals, one for each setting.

 

I'm not the only 'parent' who has commented on this too, as many of our children also attend other settings to provide wrap-around care. They have also commented that it's a bit annoying having to do everything twice, and so often just don't bother.

 

Tapestry seems to recognise when you try to log in using an email address used by both settings as you have to choose which account to access. It would be a nice add-on, to be asked when saving a parent observation - "would you like to add this to your child's journal with X'.

[FSFRebecca]

Ah I see,

Thank you for your suggestion I will put it on our list of things to consider when we are making our next round of added features and improvements :1b