Currently, the project plans to only see the babies once, so I don't need
to set up any Case Management. We can simple just enter the data for each
baby.
However, IF there was more funding found and there was a plan to follow up
these babies in a year, or something like that, would it be better to set
up Case Management now? Even though we would open the case now and close
the case on the same visit - would it make things easier in case of a
future project?? ie. Could these cases then be reopened at a future date,
IF need be?
However, you'll note that this also will roll back any data changed by the
form (and will be quite tedious if used at scale) so this probably isn't
ideal for your use case.
Unless there's a prohibitive issue I'm unaware of I would recommend just
having your forms open a case now and simply keeping them around in case
you do decide you want follow up forms in the future. This would certainly
be far easier than changing things retroactively and the memory/performance
overhead to storing these cases wouldn't become significant until you
approach a fairly large scale (on the order of 10,000 cases).
Best,
Will
···
On Mon, Jan 20, 2014 at 3:14 PM, Natasha Lelijveld < natasha.lelijveld@gmail.com> wrote:
Hi,
I am currently building forms for a new project.
Currently, the project plans to only see the babies once, so I don't need
to set up any Case Management. We can simple just enter the data for each
baby.
However, IF there was more funding found and there was a plan to follow up
these babies in a year, or something like that, would it be better to set
up Case Management now? Even though we would open the case now and close
the case on the same visit - would it make things easier in case of a
future project?? ie. Could these cases then be reopened at a future date,
IF need be?
Unless there's a prohibitive issue I'm unaware of I would recommend just
having your forms open a case now and simply keeping them around in case
you do decide you want follow up forms in the future. This would certainly
be far easier than changing things retroactively and the memory/performance
overhead to storing these cases wouldn't become significant until you
approach a fairly large scale (on the order of 10,000 cases).
Just wanted to mention that this high scale would be for an android-based
deployment. On j2me the limitations are quite a bit lower than this (can
approach a few hundred cases if you are storing lots of case properties).
···
>
> Best,
> Will
>
>
> On Mon, Jan 20, 2014 at 3:14 PM, Natasha Lelijveld < natasha.lelijveld@gmail.com> wrote:
>
>> Hi,
>>
>> I am currently building forms for a new project.
>>
>> Currently, the project plans to only see the babies once, so I don't need
>> to set up any Case Management. We can simple just enter the data for each
>> baby.
>>
>> However, IF there was more funding found and there was a plan to follow
>> up these babies in a year, or something like that, would it be better to
>> set up Case Management now? Even though we would open the case now and
>> close the case on the same visit - would it make things easier in case of a
>> future project?? ie. Could these cases then be reopened at a future date,
>> IF need be?
>>
>> Hope my question makes sense?
>>
>> Any advice for me?
>>
>> Thanks,
>>
>> Natasha
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "commcare-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to commcare-users+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "commcare-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to commcare-users+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
OK, thanks. But if I have several forms - one which opens the case. The
others which just add to the case. Does that mean that all of the case ID's
would remain in the case list? Im worried that that might be quite a
list....
Or is there some other way of doing it?
···
On 20 January 2014 22:20, Cory Zue wrote:
Hi Natasha,
Unless there's a prohibitive issue I'm unaware of I would recommend just
having your forms open a case now and simply keeping them around in case
you do decide you want follow up forms in the future. This would certainly
be far easier than changing things retroactively and the memory/performance
overhead to storing these cases wouldn't become significant until you
approach a fairly large scale (on the order of 10,000 cases).
Just wanted to mention that this high scale would be for an android-based
deployment. On j2me the limitations are quite a bit lower than this (can
approach a few hundred cases if you are storing lots of case properties).
Currently, the project plans to only see the babies once, so I don't
need to set up any Case Management. We can simple just enter the data for
each baby.
However, IF there was more funding found and there was a plan to follow
up these babies in a year, or something like that, would it be better to
set up Case Management now? Even though we would open the case now and
close the case on the same visit - would it make things easier in case of a
future project?? ie. Could these cases then be reopened at a future date,
IF need be?
Yes, all open cases for a user would appear in that user's case list. This
can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
Best,
Will
···
On Wed, Jan 22, 2014 at 7:21 AM, Natasha Lelijveld < natasha.lelijveld@gmail.com> wrote:
OK, thanks. But if I have several forms - one which opens the case. The
others which just add to the case. Does that mean that all of the case ID's
would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would recommend just
having your forms open a case now and simply keeping them around in case
you do decide you want follow up forms in the future. This would certainly
be far easier than changing things retroactively and the memory/performance
overhead to storing these cases wouldn't become significant until you
approach a fairly large scale (on the order of 10,000 cases).
Just wanted to mention that this high scale would be for an android-based
deployment. On j2me the limitations are quite a bit lower than this (can
approach a few hundred cases if you are storing lots of case properties).
Currently, the project plans to only see the babies once, so I don't
need to set up any Case Management. We can simple just enter the data for
each baby.
However, IF there was more funding found and there was a plan to follow
up these babies in a year, or something like that, would it be better to
set up Case Management now? Even though we would open the case now and
close the case on the same visit - would it make things easier in case of a
future project?? ie. Could these cases then be reopened at a future date,
IF need be?
We are using Samsung Galaxy android phones. We will have about 600 cases...
I recon about 300 of them will be active at any one time. I need to use
case sharing as it is a different team who do the recruiting and the follow
up. I will look up now how to sort and filter the list...
Thanks
···
On 22 January 2014 12:28, William Pride wrote:
Natasha,
Yes, all open cases for a user would appear in that user's case list. This
can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
OK, thanks. But if I have several forms - one which opens the case. The
others which just add to the case. Does that mean that all of the case ID's
would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would recommend
just having your forms open a case now and simply keeping them around in
case you do decide you want follow up forms in the future. This would
certainly be far easier than changing things retroactively and the
memory/performance overhead to storing these cases wouldn't become
significant until you approach a fairly large scale (on the order of 10,000
cases).
Just wanted to mention that this high scale would be for an
android-based deployment. On j2me the limitations are quite a bit lower
than this (can approach a few hundred cases if you are storing lots of case
properties).
Currently, the project plans to only see the babies once, so I don't
need to set up any Case Management. We can simple just enter the data for
each baby.
However, IF there was more funding found and there was a plan to
follow up these babies in a year, or something like that, would it be
better to set up Case Management now? Even though we would open the case
now and close the case on the same visit - would it make things easier in
case of a future project?? ie. Could these cases then be reopened at a
future date, IF need be?
With that type of phone and number of cases you shouldn't encounter any
difficulties with speed or memory. Good luck!
Best,
Will
···
On Sat, Jan 25, 2014 at 10:35 AM, Natasha Lelijveld < natasha.lelijveld@gmail.com> wrote:
We are using Samsung Galaxy android phones. We will have about 600
cases... I recon about 300 of them will be active at any one time. I need
to use case sharing as it is a different team who do the recruiting and the
follow up. I will look up now how to sort and filter the list...
Yes, all open cases for a user would appear in that user's case list.
This can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
OK, thanks. But if I have several forms - one which opens the case. The
others which just add to the case. Does that mean that all of the case ID's
would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would recommend
just having your forms open a case now and simply keeping them around in
case you do decide you want follow up forms in the future. This would
certainly be far easier than changing things retroactively and the
memory/performance overhead to storing these cases wouldn't become
significant until you approach a fairly large scale (on the order of 10,000
cases).
Just wanted to mention that this high scale would be for an
android-based deployment. On j2me the limitations are quite a bit lower
than this (can approach a few hundred cases if you are storing lots of case
properties).
Currently, the project plans to only see the babies once, so I don't
need to set up any Case Management. We can simple just enter the data for
each baby.
However, IF there was more funding found and there was a plan to
follow up these babies in a year, or something like that, would it be
better to set up Case Management now? Even though we would open the case
now and close the case on the same visit - would it make things easier in
case of a future project?? ie. Could these cases then be reopened at a
future date, IF need be?
So I was just reading about filtering the case list.... I would want to
only display cases that have not completed their 6-month follow up yet
(while still keeping ALL cases open in case of we get money for a further
follow up).
Can I do the following:
-have a question on the follow up form which says, 'has this child
completed their 6 month follow up'?
And then set my case list filter to: if the answer to the question above is
'yes', do not display them in the case list
is that possible?? Is that how you would do it??
Thanks as always
···
On 25 January 2014 15:37, William Pride wrote:
Natasha,
With that type of phone and number of cases you shouldn't encounter any
difficulties with speed or memory. Good luck!
We are using Samsung Galaxy android phones. We will have about 600
cases... I recon about 300 of them will be active at any one time. I need
to use case sharing as it is a different team who do the recruiting and the
follow up. I will look up now how to sort and filter the list...
Yes, all open cases for a user would appear in that user's case list.
This can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
OK, thanks. But if I have several forms - one which opens the case. The
others which just add to the case. Does that mean that all of the case ID's
would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would recommend
just having your forms open a case now and simply keeping them around in
case you do decide you want follow up forms in the future. This would
certainly be far easier than changing things retroactively and the
memory/performance overhead to storing these cases wouldn't become
significant until you approach a fairly large scale (on the order of 10,000
cases).
Just wanted to mention that this high scale would be for an
android-based deployment. On j2me the limitations are quite a bit lower
than this (can approach a few hundred cases if you are storing lots of case
properties).
Currently, the project plans to only see the babies once, so I don't
need to set up any Case Management. We can simple just enter the data for
each baby.
However, IF there was more funding found and there was a plan to
follow up these babies in a year, or something like that, would it be
better to set up Case Management now? Even though we would open the case
now and close the case on the same visit - would it make things easier in
case of a future project?? ie. Could these cases then be reopened at a
future date, IF need be?
If I'm understanding correctly I don't think you need to ask that question
at all - rather, you could use a hidden value (link below) to store a
boolean value like completed_followup and save this as a case property.
You'd set this value to "false" at the end of the initial registration form
and then "true" once the followup form is completed.
Then, on the case list screen, you could simply create a filter that
evaluated "not(completed_followup)" so that this will return true for all
cases that have not completed a follow up and false for all cases that have.
···
On Sat, Jan 25, 2014 at 11:25 AM, Natasha Lelijveld < natasha.lelijveld@gmail.com> wrote:
Thanks for your help Will.
So I was just reading about filtering the case list.... I would want to
only display cases that have not completed their 6-month follow up yet
(while still keeping ALL cases open in case of we get money for a further
follow up).
Can I do the following:
-have a question on the follow up form which says, 'has this child
completed their 6 month follow up'?
And then set my case list filter to: if the answer to the question above
is 'yes', do not display them in the case list
We are using Samsung Galaxy android phones. We will have about 600
cases... I recon about 300 of them will be active at any one time. I need
to use case sharing as it is a different team who do the recruiting and the
follow up. I will look up now how to sort and filter the list...
Yes, all open cases for a user would appear in that user's case list.
This can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
OK, thanks. But if I have several forms - one which opens the case.
The others which just add to the case. Does that mean that all of the case
ID's would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would recommend
just having your forms open a case now and simply keeping them around in
case you do decide you want follow up forms in the future. This would
certainly be far easier than changing things retroactively and the
memory/performance overhead to storing these cases wouldn't become
significant until you approach a fairly large scale (on the order of 10,000
cases).
Just wanted to mention that this high scale would be for an
android-based deployment. On j2me the limitations are quite a bit lower
than this (can approach a few hundred cases if you are storing lots of case
properties).
Currently, the project plans to only see the babies once, so I
don't need to set up any Case Management. We can simple just enter the data
for each baby.
However, IF there was more funding found and there was a plan to
follow up these babies in a year, or something like that, would it be
better to set up Case Management now? Even though we would open the case
now and close the case on the same visit - would it make things easier in
case of a future project?? ie. Could these cases then be reopened at a
future date, IF need be?
···
On 25 January 2014 16:35, William Pride wrote:
Natasha,
If I'm understanding correctly I don't think you need to ask that question
at all - rather, you could use a hidden value (link below) to store a
boolean value like completed_followup and save this as a case property.
You'd set this value to "false" at the end of the initial registration form
and then "true" once the followup form is completed.
Then, on the case list screen, you could simply create a filter that
evaluated "not(completed_followup)" so that this will return true for all
cases that have not completed a follow up and false for all cases that have.
So I was just reading about filtering the case list.... I would want to
only display cases that have not completed their 6-month follow up yet
(while still keeping ALL cases open in case of we get money for a further
follow up).
Can I do the following:
-have a question on the follow up form which says, 'has this child
completed their 6 month follow up'?
And then set my case list filter to: if the answer to the question above
is 'yes', do not display them in the case list
We are using Samsung Galaxy android phones. We will have about 600
cases... I recon about 300 of them will be active at any one time. I need
to use case sharing as it is a different team who do the recruiting and the
follow up. I will look up now how to sort and filter the list...
Yes, all open cases for a user would appear in that user's case list.
This can get quite large; however, you can sort and filter the list for
manageability and unless you're using a Java phone memory shouldn't be an
issue. How many active cases do you anticipate having at any time for each
user? And what type of device are you planning on using?
OK, thanks. But if I have several forms - one which opens the case.
The others which just add to the case. Does that mean that all of the case
ID's would remain in the case list? Im worried that that might be quite a
list....
Unless there's a prohibitive issue I'm unaware of I would
recommend just having your forms open a case now and simply keeping them
around in case you do decide you want follow up forms in the future. This
would certainly be far easier than changing things retroactively and the
memory/performance overhead to storing these cases wouldn't become
significant until you approach a fairly large scale (on the order of 10,000
cases).
Just wanted to mention that this high scale would be for an
android-based deployment. On j2me the limitations are quite a bit lower
than this (can approach a few hundred cases if you are storing lots of case
properties).
Currently, the project plans to only see the babies once, so I
don't need to set up any Case Management. We can simple just enter the data
for each baby.
However, IF there was more funding found and there was a plan to
follow up these babies in a year, or something like that, would it be
better to set up Case Management now? Even though we would open the case
now and close the case on the same visit - would it make things easier in
case of a future project?? ie. Could these cases then be reopened at a
future date, IF need be?