talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

scalarValuesComputed and import

SS
Susan Stone
Wed, Jul 18, 2012 2:50 PM

Anyone,

When I import structured dates, I've been loading
dateEarliestScalarValue and dateLatestScalarValue since those won't be
computed for me. Therefore, I've been setting scalarValuesComputed to false.

But it occurs that maybe I should be setting it to true so that these
values will be computed in an update through the UI.

Is that the case? What is the default if I don't set it at all?

Thanks,
Susan

Anyone, When I import structured dates, I've been loading dateEarliestScalarValue and dateLatestScalarValue since those won't be computed for me. Therefore, I've been setting scalarValuesComputed to false. But it occurs that maybe I should be setting it to true so that these values will be computed in an update through the UI. Is that the case? What is the default if I don't set it at all? Thanks, Susan
AR
Aron Roberts
Wed, Jul 18, 2012 4:35 PM

Hi Susan,

My understanding of the purpose of the scalarValuesComputed flag
appears in an old, off-list message below.

Comments and updates on this from those who might know more about
this are welcomed!

Aron

---------- Forwarded message ----------
From: Aron Roberts aron@socrates.berkeley.edu
Date: Thu, Nov 17, 2011 at 2:37 PM
Subject: scalarValuesComputed in structured date
To: "Zenevich, Yura" yzenevich@ocad.ca
Cc: Chris Martin csm22@caret.cam.ac.uk, Rick Jaffe
rjaffe@berkeley.edu, Patrick Schmitz pschmitz@berkeley.edu

Hi Yura,

Re your IRC questions / comments about flags in structured dates:

[1:51pm] yura: aronr: just to double check scalarValuesComputed is an indicator for UI to compute the scalars
[1:51pm] yura: right ?

Yes, that's what I understand as well.  Most or all of the
'computed' flags seem to mean, AIUI, that "a value in another field -
the field controlled by this flag - should be (re)computed whenever
appropriate."  (They may also have the corollary meaning that, "if
there is a value in that other field, it was computed rather than
provided," but I'm not certain of that one.)

scalarValuesComputed = true: the two scalar values should be computed
scalarValuesComputed = false: the two scalar values should not be computed;
for instance, when a client has imported those values and
doesn't want them ever to be changed

[1:55pm] yura: aronr: fyi i committed scalar stuff to UI , it has a flag that's defaulted to false displayScalars for displaying

That'll be handy for Chris Pott and anyone else who wishes to make
those fields visible in the UI.

and it will not compute if the  scalarValuesComputed for a specific structured date is not preset to true

That seems consistent with the logic above, if I'm understanding
this correctly.

Aron

--

On Wed, Jul 18, 2012 at 7:50 AM, Susan Stone
sstone@socrates.berkeley.edu wrote:

Anyone,

When I import structured dates, I've been loading dateEarliestScalarValue
and dateLatestScalarValue since those won't be computed for me. Therefore,
I've been setting scalarValuesComputed to false.

But it occurs that maybe I should be setting it to true so that these values
will be computed in an update through the UI.

Is that the case? What is the default if I don't set it at all?

Thanks,
Susan


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Susan, My understanding of the purpose of the scalarValuesComputed flag appears in an old, off-list message below. Comments and updates on this from those who might know more about this are welcomed! Aron ---------- Forwarded message ---------- From: Aron Roberts <aron@socrates.berkeley.edu> Date: Thu, Nov 17, 2011 at 2:37 PM Subject: scalarValuesComputed in structured date To: "Zenevich, Yura" <yzenevich@ocad.ca> Cc: Chris Martin <csm22@caret.cam.ac.uk>, Rick Jaffe <rjaffe@berkeley.edu>, Patrick Schmitz <pschmitz@berkeley.edu> Hi Yura, Re your IRC questions / comments about flags in structured dates: > [1:51pm] yura: aronr: just to double check scalarValuesComputed is an indicator for UI to compute the scalars > [1:51pm] yura: right ? Yes, that's what I understand as well. Most or all of the 'computed' flags seem to mean, AIUI, that "a value in another field - the field controlled by this flag - should be (re)computed whenever appropriate." (They *may* also have the corollary meaning that, "if there is a value in that other field, it was computed rather than provided," but I'm not certain of that one.) scalarValuesComputed = true: the two scalar values should be computed scalarValuesComputed = false: the two scalar values should not be computed; for instance, when a client has imported those values and doesn't want them ever to be changed > [1:55pm] yura: aronr: fyi i committed scalar stuff to UI , it has a flag that's defaulted to false displayScalars for displaying That'll be handy for Chris Pott and anyone else who wishes to make those fields visible in the UI. > and it will not compute if the scalarValuesComputed for a specific structured date is not preset to true That seems consistent with the logic above, if I'm understanding this correctly. Aron -- On Wed, Jul 18, 2012 at 7:50 AM, Susan Stone <sstone@socrates.berkeley.edu> wrote: > Anyone, > > When I import structured dates, I've been loading dateEarliestScalarValue > and dateLatestScalarValue since those won't be computed for me. Therefore, > I've been setting scalarValuesComputed to false. > > But it occurs that maybe I should be setting it to true so that these values > will be computed in an update through the UI. > > Is that the case? What is the default if I don't set it at all? > > Thanks, > Susan > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
SS
Susan Stone
Wed, Jul 18, 2012 5:17 PM

Thanks, Aron. This helps. Looks like I should set it to true so they
will be computed in the UI in the future. (I was interpreting it as the
possible corollary meaning, I think left over from displayNameComputed
when if they were computed in the services my values would be ignored.
As long as it is a message to the UI there is no danger of that.)

Susan

On 07/18/2012 09:35 AM, Aron Roberts wrote:

Hi Susan,

My understanding of the purpose of the scalarValuesComputed flag

appears in an old, off-list message below.

Comments and updates on this from those who might know more about

this are welcomed!

Aron

---------- Forwarded message ----------
From: Aron Roberts aron@socrates.berkeley.edu
Date: Thu, Nov 17, 2011 at 2:37 PM
Subject: scalarValuesComputed in structured date
To: "Zenevich, Yura" yzenevich@ocad.ca
Cc: Chris Martin csm22@caret.cam.ac.uk, Rick Jaffe
rjaffe@berkeley.edu, Patrick Schmitz pschmitz@berkeley.edu

Hi Yura,

Re your IRC questions / comments about flags in structured dates:

[1:51pm] yura: aronr: just to double check scalarValuesComputed is an indicator for UI to compute the scalars
[1:51pm] yura: right ?

Yes, that's what I understand as well.  Most or all of the

'computed' flags seem to mean, AIUI, that "a value in another field -
the field controlled by this flag - should be (re)computed whenever
appropriate."  (They may also have the corollary meaning that, "if
there is a value in that other field, it was computed rather than
provided," but I'm not certain of that one.)

scalarValuesComputed = true: the two scalar values should be computed
scalarValuesComputed = false: the two scalar values should not be computed;
    for instance, when a client has imported those values and

doesn't want them ever to be changed

[1:55pm] yura: aronr: fyi i committed scalar stuff to UI , it has a flag that's defaulted to false displayScalars for displaying

That'll be handy for Chris Pott and anyone else who wishes to make

those fields visible in the UI.

and it will not compute if the  scalarValuesComputed for a specific structured date is not preset to true

That seems consistent with the logic above, if I'm understanding

this correctly.

Aron

--

On Wed, Jul 18, 2012 at 7:50 AM, Susan Stone
sstone@socrates.berkeley.edu wrote:

Anyone,

When I import structured dates, I've been loading dateEarliestScalarValue
and dateLatestScalarValue since those won't be computed for me. Therefore,
I've been setting scalarValuesComputed to false.

But it occurs that maybe I should be setting it to true so that these values
will be computed in an update through the UI.

Is that the case? What is the default if I don't set it at all?

Thanks,
Susan


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Thanks, Aron. This helps. Looks like I should set it to true so they will be computed in the UI in the future. (I was interpreting it as the possible corollary meaning, I think left over from displayNameComputed when if they were computed in the services my values would be ignored. As long as it is a message to the UI there is no danger of that.) Susan On 07/18/2012 09:35 AM, Aron Roberts wrote: > Hi Susan, > > My understanding of the purpose of the scalarValuesComputed flag > appears in an old, off-list message below. > > Comments and updates on this from those who might know more about > this are welcomed! > > Aron > > ---------- Forwarded message ---------- > From: Aron Roberts <aron@socrates.berkeley.edu> > Date: Thu, Nov 17, 2011 at 2:37 PM > Subject: scalarValuesComputed in structured date > To: "Zenevich, Yura" <yzenevich@ocad.ca> > Cc: Chris Martin <csm22@caret.cam.ac.uk>, Rick Jaffe > <rjaffe@berkeley.edu>, Patrick Schmitz <pschmitz@berkeley.edu> > > > Hi Yura, > > Re your IRC questions / comments about flags in structured dates: > >> [1:51pm] yura: aronr: just to double check scalarValuesComputed is an indicator for UI to compute the scalars >> [1:51pm] yura: right ? > > Yes, that's what I understand as well. Most or all of the > 'computed' flags seem to mean, AIUI, that "a value in another field - > the field controlled by this flag - should be (re)computed whenever > appropriate." (They *may* also have the corollary meaning that, "if > there is a value in that other field, it was computed rather than > provided," but I'm not certain of that one.) > > scalarValuesComputed = true: the two scalar values should be computed > scalarValuesComputed = false: the two scalar values should not be computed; > for instance, when a client has imported those values and > doesn't want them ever to be changed > >> [1:55pm] yura: aronr: fyi i committed scalar stuff to UI , it has a flag that's defaulted to false displayScalars for displaying > > That'll be handy for Chris Pott and anyone else who wishes to make > those fields visible in the UI. > >> and it will not compute if the scalarValuesComputed for a specific structured date is not preset to true > > That seems consistent with the logic above, if I'm understanding > this correctly. > > Aron > > -- > > On Wed, Jul 18, 2012 at 7:50 AM, Susan Stone > <sstone@socrates.berkeley.edu> wrote: >> Anyone, >> >> When I import structured dates, I've been loading dateEarliestScalarValue >> and dateLatestScalarValue since those won't be computed for me. Therefore, >> I've been setting scalarValuesComputed to false. >> >> But it occurs that maybe I should be setting it to true so that these values >> will be computed in an update through the UI. >> >> Is that the case? What is the default if I don't set it at all? >> >> Thanks, >> Susan >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org