Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review the numbering of all newly numeric codes #48

Closed
Bjwebb opened this issue Aug 12, 2014 · 15 comments
Closed

Review the numbering of all newly numeric codes #48

Bjwebb opened this issue Aug 12, 2014 · 15 comments
Assignees
Milestone

Comments

@Bjwebb Bjwebb added this to the 2.01 Iteration 3 milestone Aug 12, 2014
@Bjwebb
Copy link
Contributor Author

Bjwebb commented Aug 18, 2014

@bill-anderson Could you review the new numbering used for each of these codelists?

@Bjwebb
Copy link
Contributor Author

Bjwebb commented Aug 22, 2014

Another proposal might be to ensure that the default value for a Vocabulary is always numbered 1. ie. that SectorVocabulary has code 1 as 5 digit DAC codes. Note that SectorVocabulary probably also has too many codes on it, see #43

@bill-anderson
Copy link

Agree with 1 = default value. Not fussed about others. I'm sure @stevieflow will have a grand plan

@bill-anderson bill-anderson assigned Bjwebb and unassigned bill-anderson Sep 2, 2014
@stevieflow
Copy link
Contributor

The concern with ActivityDate was that the numeric codes may not have "flowed". Granted, this may seem arbitary, but we might want to decide whether to order the numbers by date period (start dates, then end dates) rather type (actuals, then planned)....

@Bjwebb
Copy link
Contributor Author

Bjwebb commented Sep 3, 2014

Renumbered SectorVocabulary in this commit. I've glanced through the other codelists, and the only other potential issue I spot is OrganisationRole now has Accountable as code 1 (because I numbered them alphabetically), but Accountable is actually one of the less used codes.

@stevieflow I agree that ActivityDate might also be useful numbered more chronologically. How about:

  • 1- start-planned
  • 2 - start-actual
  • 3 - end-planned
  • 4 - end-actual

@stevieflow
Copy link
Contributor

ok thanks

Agree with the new numbers for ActivityDateType

@bill-anderson any thoughts on OrganisationRole ?

Bjwebb added a commit that referenced this issue Sep 4, 2014
@Bjwebb Bjwebb assigned bill-anderson and unassigned stevieflow Sep 4, 2014
@Bjwebb Bjwebb modified the milestones: 2.01 Final, 2.01 Iteration 3 Sep 9, 2014
@stevieflow
Copy link
Contributor

Looking at OrganisationRole - @bill-anderson

http://dev.iatistandard.org/201/codelists/OrganisationRole/

Could these be in a different order, perhaps?:

Funcing
Accountable
Extending
Implementing

@bill-anderson
Copy link

Could be. I agree with whatever you think is best

@stevieflow
Copy link
Contributor

Definitive answer!

1 Funding
2 Accountable
3 Extending
4 Implementing

seems more in line with "flow" than:

1 Accountable
2 Extending
3 Funding
4 Implementing

? @jonihillman @iatisupport ?

@wendyrogers
Copy link

Definitive answer looks about right to me!

@stevieflow
Copy link
Contributor

Do we take the revised order as a change for @Bjwebb to implement therefore?

@bill-anderson
Copy link

As he said - "I agree with whatever you think is best"

@stevieflow stevieflow assigned Bjwebb and unassigned bill-anderson Sep 23, 2014
@stevieflow
Copy link
Contributor

Assigned to @Bjwebb to implement

@stevieflow
Copy link
Contributor

@Bjwebb I have created new Issues for the three codelists that need renumbering

Aside from that, the only comment I can see in this Issue that may need some action is #48 (comment) - is this correct (or can we close this?)?

@Bjwebb
Copy link
Contributor Author

Bjwebb commented Sep 23, 2014

I think this issue can now be closed.

@Bjwebb Bjwebb closed this as completed Sep 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants