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

Define 'Preferred Standard' vs 'Standard' indicators and show on left menu #26

Open
gilliankerr opened this issue Dec 16, 2016 · 1 comment

Comments

@gilliankerr
Copy link

@gilliankerr commented on Fri Nov 04 2016

We may not even want this; we could use Rating (with tags and slots) or Ranking (using Aristotle built in functionality) instead.


@LegoStormtroopr commented on Sun Nov 06 2016

The 11179 spec allows each agency to define what makes metadata such as an Indicator "standard" - if we make LogicalOutcomes a registration authority (which is accurate because you are registering metadata) then its up to you to define standard (and all of the status levels).

As for if you should use these statuses - I would recommend that you should simply because its baked into 11179. For the time being I think all of the indicators have been registered to the level of "recorded" (which they are) and then we need to determine what makes metadata recorded versus standard versus incomplete etc...

@gilliankerr
Copy link
Author

I agree. Let's use it. A given indicator may be Preferred Standard in one collection, Standard in another, and just Qualified in a third. The indicator detail sheets should show all the collections in which it is registered. Then the rating filter in the menu could be a combination score showing the number of collections in which it is preferred, and the number of collections in which it is standard (for example). In terms of ratings within a collection, that would be defined by each registrar.

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

1 participant