Support prev/next work navigation to WorkEdit

[rococodogs]

Currently in MetaDB, users are able to navigate works in a collection using a set of controls at the top of the Item Metadata screen:

That was/is the only way to navigate to items from within a collection. Now that we'll a few ways to find / navigate works, is this still desired? Is this even a possibility without a ton of work on the lafayette-concerns side?

[eluhrs]

I would say that the access style navigation would still be highly useful as it is makes cataloging easier. If implementing this functionality is difficult, then I would need to understand other potential workflows.

E

On Nov 3, 2016, at 7:39 AM, adam malantonio notifications@github.com wrote:

Currently in MetaDB, users are able to navigate works in a collection using a set of controls at the top of the Item Metadata screen:

That was/is the only way to navigate to items from within a collection. Now that we'll a few ways to find / navigate works, is this still desired? Is this even a possibility without a ton of work on the lafayette-concerns side?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jrgriffiniii]

I would tend to agree that retaining an index for the interface may have some value, but I cannot see this as useful outside of existing, structured collections when offered at the level of individual Works.

The case I envision is one in which the user performs a full-text search, and then facets upon the result set. As the page index for this result set is already present, it is my speculation that an additional numeric index for the Works themselves in the result set may be disorienting.