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

truncated author list #100

Closed
pitman opened this issue Oct 14, 2011 · 3 comments
Closed

truncated author list #100

pitman opened this issue Oct 14, 2011 · 3 comments

Comments

@pitman
Copy link

pitman commented Oct 14, 2011

Author listing for erdos

http://bibsoup.net/test/erdos

used to be a complete list (approx 500 author names).
Now its truncated to names starting with A , B or C.
Best if possible to show the complete list.
For big enough author lists we will have to truncate.
Should do this by a "more .... " which redirects to a display
of author entity pages, just like has been done for collections.

Even for short author lists, please provide a break out to more comprehensive author listing,
allowing inclusion of data from person records in the display.

@markmacgillivray
Copy link
Contributor

Increased author listing size back to what it was. Will look into pagination of author lists as part of the next development. Closing this ticket for now.

@pitman
Copy link
Author

pitman commented Oct 28, 2011

markmacgillivray reply@reply.github.com wrote:

Increased author listing size back to what it was.

Erdos list stops now at P. Please increase the size of list say 550 so it can at least
be complete on this dataset which is a basic benchmark for the system.

Will look into pagination of author lists as part of the next development. Closing this ticket for now.

Then this issue should be on feature request somewhere. Please places somewhere I and others
can see all of the feature requests and we can allocate priorities, place on a roadmap, ....

many thanks!

--Jim

@markmacgillivray
Copy link
Contributor

We already have the feature requests that we require in the user stories spreadsheet, which you have access to. e,g, write a user story that demonstrates the feature, and give it an importance value. Then when we start the next round of coding we will choose which of these to follow up first. (Probably next week.) However, a generic feature requests section that anyone can access is a good idea, I will add it to the project website.

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

2 participants