Hi Richard and Georgina,
Two things. I have changed the terminology from "state" to "stage" in the story definition. I think the original "state" terminology was too close to the existing fixed review statuses (Requested, In Progress, Complete) we have in the system and could have been confusing.
I think "stage" better represents what we are trying to model here, i.e. the status (or state) of the review remains "In Progress" but it needs to pass through a number of tenant-defined stages (e.g. at digitisation, with acquisitions team, etc...) before it can be considered complete.
Onto the assigning a user - We are currently in progress with an "Assign list owner" story (XIP-2190). This will put in place the necessary dialogues and facilities to search for people and assign them as the owner of a list.
This is essentially the same functionality as setting an assignee for a review. So, instead of bundling that functionality into the "stages" story (which is close to being picked up), I have added a new story (XIP-2226) on the stack. We will let XIP-2190 and the stages story complete naturally, then the addition of assignees should be a logical and easy extension.
The story description is as follows:
In a similar way to XIP-2190, a user can be assigned to any review "in progress".
The assignment and search works in the same way as XIP-2190 (search and auto suggest).
From the all reviews screen, there is a new column "Assigned to". This column includes the name of the user currently assigned to the review. The column is sortable.
From the top of the all reviews screen the user can filter the table on "Assigned/Unassigned reviews" (i.e. reviews with, or without, an assigned user.
I just wanted to share the story description I have sent to the developers, to make sure we implement this as expected:
Every acquisition review with status of "Started" can also optionally have a "state" assigned with it.
States are configured at the tenancy level and therefore can be different for each tenant.
Optionally a default state can also be configured.
Setting a state
When a review is initially started, if a default state is set in tenancy config, the review automatically assumes the default state.
From hereon in, the user can change the state of any in progress review using a drop down at the top of the list review screen. The state can be unset completely if the user selects the empty value in the drop down. Whilst the state is being saved (following the user selecting a new value) a progress spinny is shown to the right of the state drop down.
Creating data to allow reporting at a later date
This story also introduces the notion of events for reviews. This allows us to report on time spent in status/state at a later date. The events feed works in the same way as list/tenancy events in the existing codebase and uses the same data model.
Every time a state is set or changed, including when the state is set via the defaulting process, an event is written to the /events log in the review.
13 votesbacklog · 4 comments · Talis Aspire Reading Lists » Viewing Lists & Items · Flag idea as inappropriate… · Admin →
We won't be able to display the email address as this is a public page, and that could open up the individual to spam, but we could show the first and last name of the individual.
As part of integration theme
On 1) the API as it is returns matching lists. Since importances are actually a property of items, not lists, how do you see this working? Instead, should we be thinking along the lines of extending the api like this:
This could return the item URIs that reference the ISBN, along with the importance and the corresponding list URI the item is on.
On 2, is the real reason behind this (multiple ISBNs in a hit) because you want to do some xISBN style function, i.e. send me back data not just for this ISBN, but all related ISBNs? If so, we are doing some research work in Aspire to actually marry up editions (you'll see the first fruits of this soon in talisaspire.com, which will tie up references at work level).
27 votes7 comments · Talis Aspire Reading Lists » Viewing Lists & Items · Flag idea as inappropriate… · Admin →
Tagging is something we plan to address and it is in backlog. However, it is not yet scoped or prioritised but we will update this idea as we progress.
I've re-titled this issue as "Tag items" (was Tag Items as 'Electronic Resource') as tagging could be used for a number of purposes including marking things as electronic resources.
User management is not in our near term development focus so it has been moved to the longer term backlog.
Ideas may be graduated from the backlog as we get through the ones that are planned.
Peter, do you know that you could already achieve this functionality today with a simple change to your existing permissions setup? Please contact us to discuss this in more detail.chrisc shared this idea ·