affiliations percentage
Christian, Part 2 of the planned ACIS-RAS changes includes:
For multiple affiliations, let users specify percentages for each. Support it in ReDIF profile export.
I need a detailed description of this feature. How will it look and behave? In particular, i have the following questions: - would we allow entering any free number between 0 and 100? (as a text input field.) Or do we allow choice of only certain values, like 10, 20, 30, 40, etc? (as a drop-down select control) - do we ensure that the sum of the percentages equals exactly 100 or not? - what happens when a user removes an affiliations (with some percentage assigned to it)? - how do we treat a case of three equally-important affiliations? (33%? 33.33%? 30%?) - do we sort the affiliations in the order of decreasing percentage automatically? I can prepare mockups after you answer these questions. -ivan
On Sun, 13 Nov 2011, Ivan Kurmanov wrote:
Christian,
Part 2 of the planned ACIS-RAS changes includes:
For multiple affiliations, let users specify percentages for each. Support it in ReDIF profile export.
I need a detailed description of this feature. How will it look and behave? In particular, i have the following questions:
- would we allow entering any free number between 0 and 100? (as a text input field.) Or do we allow choice of only certain values, like 10, 20, 30, 40, etc? (as a drop-down select control)
I think free numbers are best
- do we ensure that the sum of the percentages equals exactly 100 or not?
Yes. This could be enforced either by not allowing the person to go further with the total of 100, or by adjusting them proportioannly to a total to 100.
- what happens when a user removes an affiliations (with some percentage assigned to it)?
See above.
- how do we treat a case of three equally-important affiliations? (33%? 33.33%? 30%?)
34, 33, 33.
- do we sort the affiliations in the order of decreasing percentage automatically?
That could be useful, as it is often requested from users. Additional point: say affiliation A is Dept X, School Y, University Z B is School Y, University Z C is Think Tank W then it must always be that B>=A, and B+C=100. The reason is that A is part of B.
I can prepare mockups after you answer these questions.
-ivan
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
'Christian Zimmermann' writes
Additional point: say affiliation A is Dept X, School Y, University Z B is School Y, University Z C is Think Tank W
then it must always be that B>=A, and B+C=100. The reason is that A is part of B.
Do you want to enforce this at the point of data entry? I don't think ACIS reads a relational structure of institutions at this time. So this would require changes at the back end. This would also have an effect on searches as well. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorprofile.org/pkr1 skype: thomaskrichel
On Sun, 13 Nov 2011, Thomas Krichel wrote:
'Christian Zimmermann' writes
Additional point: say affiliation A is Dept X, School Y, University Z B is School Y, University Z C is Think Tank W
then it must always be that B>=A, and B+C=100. The reason is that A is part of B.
Do you want to enforce this at the point of data entry? I don't think ACIS reads a relational structure of institutions at this time. So this would require changes at the back end. This would also have an effect on searches as well.
Not sure. This can be enforced only on this page, as the name string of B is a substring of A. In any case, there are going to be imperfections. For example, when an Economics Department moves out of a Business School, the constraint above suddenly is not valid when I modify the institutional record, without the author visiting the profile. I guess this is sufficiently rare to be dealt with on a case-by-case basis.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorprofile.org/pkr1 skype: thomaskrichel
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
'Christian Zimmermann' writes
In any case, there are going to be imperfections.
You will have to think about how to deal with these, at composition time or via an alert to an administrator. At composition time seems rather tricky to me. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorprofile.org/pkr1 skype: thomaskrichel
On Mon, 14 Nov 2011, Thomas Krichel wrote:
'Christian Zimmermann' writes
In any case, there are going to be imperfections.
You will have to think about how to deal with these, at composition time or via an alert to an administrator. At composition time seems rather tricky to me.
I already do, for example when there are mergers, I need to make sure affiliations are transfered. As I said, this can and has been dealt with on a case-by-case basis. It would complicate RAS to much to deal with this internally.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorprofile.org/pkr1 skype: thomaskrichel
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
Christian, Your general requirements are clear, and I'm writing a kind of spec with mockups to finalize the discussion. But:
Additional point: say affiliation A is Dept X, School Y, University Z B is School Y, University Z C is Think Tank W
then it must always be that B>=A, and B+C=100. The reason is that A is part of B.
This is a complication that goes beyond the scope of the original item in our agreement, which was:
For multiple affiliations, let users specify percentages for each. Support it in ReDIF profile export.
So I do not promise you this additional feature. But we can push it to the end of the development queue. And when I'm done with the other features (as agreed), I may additionally do something like this (or maybe there will be other items of the similar status) as a free contribution to the project. Or alternatively, if you believe this is really important, we must agree on excluding some other work from the scope of the project. Let me know if this is not appropriate to discuss this on this list. -ivan
Here is my affiliations draft. I could make this into a google document, but let's start with plain text: Affiliations' percentages spec draft with questions I'm using the "we" pronoun in the following mainly to mean the RAS/ACIS system. We let users enter percentage for each affiliations that they list in their profile. We show an input box for each affiliation, with some label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc (We probably need the percent sign (%) near the input boxes, or in the column title?) – What would the input box label or the column label be? – What label should the button have? The [Save share changes] button can be disabled (grayed out) until the user modifies one of the given percentage values (JavaScript). By default, when a user first sees this screen with this feature enabled, we calculate the percentage automatically, splitting the 100% equally, in the best possible way (e.g. 34, 33, 33 in case of three institutions). User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar. – Do we need such message? What text would you like to have there? If a person deletes an affiliation, we adjust the remaining numbers in the same way. While adjusting the numbers we always ensure that the total sum of them is 100, in the best way possible, while keeping the individual numbers in the integer range 1-99. The numbers entered by the users as a share are also enforced to be numbers in the integer range 1-99. If a user enters a non-numeric value, or a non-integer value, ACIS would show an error message "Invalid share number. Use an integer between 1 and 99." and it would bring back the displayed share of that affiliation to it's previous value. If the user has only one affiliation, we do not show the Share column, the input boxes, the [Save share changes] button. (And no Workplace-Share attribute is written into the ReDIF template in that case.) If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value. – What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]" – Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better? – Anything else to clarify or to consider? -Ivan
On Wed, 16 Nov 2011, Ivan Kurmanov wrote:
Here is my affiliations draft. I could make this into a google document, but let's start with plain text:
Affiliations' percentages spec draft with questions
I'm using the "we" pronoun in the following mainly to mean the RAS/ACIS system.
We let users enter percentage for each affiliations that they list in their profile. We show an input box for each affiliation, with some label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e
Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc
I like this second one more. It clusters less the left hand side.
(We probably need the percent sign (%) near the input boxes, or in the column title?)
– What would the input box label or the column label be? – What label should the button have?
They are OK as in the mockup. But I suggest adding at the bottom of the column a "total" box, that adds up the shares, with a % sign. Javascript can add the shares live, as I have seen elsewhere. Of course, what happens if someone does not have Javascript turned on?
The [Save share changes] button can be disabled (grayed out) until the user modifies one of the given percentage values (JavaScript).
By default, when a user first sees this screen with this feature enabled, we calculate the percentage automatically, splitting the 100% equally, in the best possible way (e.g. 34, 33, 33 in case of three institutions).
User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar.
– Do we need such message? What text would you like to have there?
Confirmation is always good.
If a person deletes an affiliation, we adjust the remaining numbers in the same way.
While adjusting the numbers we always ensure that the total sum of them is 100, in the best way possible, while keeping the individual numbers in the integer range 1-99.
The numbers entered by the users as a share are also enforced to be numbers in the integer range 1-99. If a user enters a non-numeric value, or a non-integer value, ACIS would show an error message "Invalid share number. Use an integer between 1 and 99." and it would bring back the displayed share of that affiliation to it's previous value.
If the user has only one affiliation, we do not show the Share column, the input boxes, the [Save share changes] button. (And no Workplace-Share attribute is written into the ReDIF template in that case.)
If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value.
– What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]"
SOmething like "Please adjust shares after deletion"?
– Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better?
– Anything else to clarify or to consider?
We may need an external link on or next to "Share" with some explanations. I propose: "For multiple affiliations, please attribute a share to each. These will be used to determine the main affiliation and allocate ranking scores across affiliations. With affiliations in different regions or countries, your ranking scores will also be weighted accordingly."
-Ivan
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e
Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc
I like this second one more. It clusters less the left hand side.
ok.
(We probably need the percent sign (%) near the input boxes, or in the column title?)
– What would the input box label or the column label be? – What label should the button have?
They are OK as in the mockup. But I suggest adding at the bottom of the column a "total" box, that adds up the shares, with a % sign. Javascript can add the shares live, as I have seen elsewhere.
Yes, and I like the idea.
Of course, what happens if someone does not have Javascript turned on?
It would simply not react to share changes, or will be empty at all.
User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar.
– Do we need such message? What text would you like to have there?
Confirmation is always good.
okay
If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value.
– What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]"
SOmething like "Please adjust shares after deletion"?
hmm.
– Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better?
– Anything else to clarify or to consider?
We may need an external link on or next to "Share" with some explanations. I propose:
"For multiple affiliations, please attribute a share to each. These will be used to determine the main affiliation and allocate ranking scores across affiliations. With affiliations in different regions or countries, your ranking scores will also be weighted accordingly."
okay. I think that's enough for a first implementation, and then we would iron out the details, if any. -ivan
Christian, Please review the first implementation of affiliation shares at http://ras.openlib.org/ . It is quite rough at SOME edges: - shares are not exported to redif - no total box - no confirmation shown when an affiliation is deleted or added or when shares are modified - not well tested With the Share column added the Delete button now depends on JavaScript in the browser. They won't work when/if javascript is disabled, but it should show a warning for that case. -ivan On Mon, Nov 21, 2011 at 11:58 AM, Ivan Kurmanov <duraley@gmail.com> wrote:
label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e
Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc
I like this second one more. It clusters less the left hand side.
ok.
(We probably need the percent sign (%) near the input boxes, or in the column title?)
– What would the input box label or the column label be? – What label should the button have?
They are OK as in the mockup. But I suggest adding at the bottom of the column a "total" box, that adds up the shares, with a % sign. Javascript can add the shares live, as I have seen elsewhere.
Yes, and I like the idea.
Of course, what happens if someone does not have Javascript turned on?
It would simply not react to share changes, or will be empty at all.
User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar.
– Do we need such message? What text would you like to have there?
Confirmation is always good.
okay
If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value.
– What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]"
SOmething like "Please adjust shares after deletion"?
hmm.
– Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better?
– Anything else to clarify or to consider?
We may need an external link on or next to "Share" with some explanations. I propose:
"For multiple affiliations, please attribute a share to each. These will be used to determine the main affiliation and allocate ranking scores across affiliations. With affiliations in different regions or countries, your ranking scores will also be weighted accordingly."
okay.
I think that's enough for a first implementation, and then we would iron out the details, if any.
-ivan
Looks good. Does the way you implemented this actually require Javascript? It could be done without it, right?, as there is not total box. Clicking on "saving shares" rebalances as desired. Also, I notice one cannot search for affiliation locations any more. Applies to live version as well. On Fri, 16 Dec 2011, Ivan Kurmanov wrote:
Christian,
Please review the first implementation of affiliation shares at http://ras.openlib.org/ . It is quite rough at SOME edges:
- shares are not exported to redif - no total box - no confirmation shown when an affiliation is deleted or added or when shares are modified - not well tested
With the Share column added the Delete button now depends on JavaScript in the browser. They won't work when/if javascript is disabled, but it should show a warning for that case.
-ivan
On Mon, Nov 21, 2011 at 11:58 AM, Ivan Kurmanov <duraley@gmail.com> wrote:
label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e
Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc
I like this second one more. It clusters less the left hand side.
ok.
(We probably need the percent sign (%) near the input boxes, or in the column title?)
– What would the input box label or the column label be? – What label should the button have?
They are OK as in the mockup. But I suggest adding at the bottom of the column a "total" box, that adds up the shares, with a % sign. Javascript can add the shares live, as I have seen elsewhere.
Yes, and I like the idea.
Of course, what happens if someone does not have Javascript turned on?
It would simply not react to share changes, or will be empty at all.
User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar.
– Do we need such message? What text would you like to have there?
Confirmation is always good.
okay
If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value.
– What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]"
SOmething like "Please adjust shares after deletion"?
hmm.
– Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better?
– Anything else to clarify or to consider?
We may need an external link on or next to "Share" with some explanations. I propose:
"For multiple affiliations, please attribute a share to each. These will be used to determine the main affiliation and allocate ranking scores across affiliations. With affiliations in different regions or countries, your ranking scores will also be weighted accordingly."
okay.
I think that's enough for a first implementation, and then we would iron out the details, if any.
-ivan
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
On Sat, Dec 17, 2011 at 12:30 AM, Christian Zimmermann <zimmermann@stlouisfed.org> wrote:
Looks good.
Does the way you implemented this actually require Javascript? It could be done without it, right?, as there is not total box.
It does require JavaScript even without the total box. Long story, but without it the form could delete an affiliation when the user have just tried to edit the shares. And for that to happen just this one simple thing has to happen: user enters an input box with share numbers and presses Enter. That submits the form in the same way, as if user clicked on a delete button of an affiliation. No way for the software on the server to tell the difference. So, client-side software comes to help.
Clicking on "saving shares" rebalances as desired.
good!
Also, I notice one cannot search for affiliation locations any more. Applies to live version as well.
This is something Thomas has removed in his version. I've put it back, except for search instructions. Do we need the instructions? -ivan
On Fri, 16 Dec 2011, Ivan Kurmanov wrote:
Christian,
Please review the first implementation of affiliation shares at http://ras.openlib.org/ . It is quite rough at SOME edges:
- shares are not exported to redif - no total box - no confirmation shown when an affiliation is deleted or added or when shares are modified - not well tested
With the Share column added the Delete button now depends on JavaScript in the browser. They won't work when/if javascript is disabled, but it should show a warning for that case.
-ivan
On Mon, Nov 21, 2011 at 11:58 AM, Ivan Kurmanov <duraley@gmail.com> wrote:
label next to it. For example, in this mockup I use "Share:" as the label: http://www.screencast.com/t/qza127hJ0e
Or we change the affiliations display to a table view and put those input boxes into a column, with the submit button below the column. http://www.screencast.com/t/cNotuQQJ8uc
I like this second one more. It clusters less the left hand side.
ok.
(We probably need the percent sign (%) near the input boxes, or in the column title?)
– What would the input box label or the column label be? – What label should the button have?
They are OK as in the mockup. But I suggest adding at the bottom of the column a "total" box, that adds up the shares, with a % sign. Javascript can add the shares live, as I have seen elsewhere.
Yes, and I like the idea.
Of course, what happens if someone does not have Javascript turned on?
It would simply not react to share changes, or will be empty at all.
User may change the numbers and submit the change by clicking the [Save share changes] button. Then we process the share values given and adjust it proportionally to a total of 100%. And we display the same screen with adjusted numbers and with the affiliations sorted in the order of decreasing share. Additionally, we show a confirmation message in the top part of the page, saying "The affiliation shares have been saved." or similar.
– Do we need such message? What text would you like to have there?
Confirmation is always good.
okay
If the user has opened the affiliations page, has modified the Share value for one or more affiliations, but then clicked on the [Delete] button of some other affiliation, his change to the share values is not saved. We may show a confirmation dialog if he wants to submit the form without saving the share value.
– What should be the confirmation dialog text then? "The share changes will not be saved. [Cancel] [OK]"
SOmething like "Please adjust shares after deletion"?
hmm.
– Or alternatively, we could save the shares even in this case. Save the shares AND delete the affiliation at the same time. Is this better?
– Anything else to clarify or to consider?
We may need an external link on or next to "Share" with some explanations. I propose:
"For multiple affiliations, please attribute a share to each. These will be used to determine the main affiliation and allocate ranking scores across affiliations. With affiliations in different regions or countries, your ranking scores will also be weighted accordingly."
okay.
I think that's enough for a first implementation, and then we would iron out the details, if any.
-ivan
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
participants (3)
-
'Christian Zimmermann' -
Ivan Kurmanov -
Thomas Krichel