search

ewg118 / numishare

Numishare is an open source suite of applications for managing digital cultural heritage artifacts, with a particular focus on coins and medals.
Apache License 2.0
40 stars 19 forks source link

Mantis - database extraction related issues #14

Closed RomanCoins closed 11 years ago

RomanCoins commented 11 years ago

Hi Ethan, trying to workout around the available weights in a sample of our database. When I sort results in Mantis 2, for instance by year, it works fine. Then when you download the data using CSV, it does not affect the order in the database. It actually provides the user with the same order, irrespective of the way you did sort the data out.
This is obviously something one can address once he managed to convert the CSV into Excel, but this is not that straightforward a process. Is there a way the sorting functions would affect the CSV downloads? Thanks. Gilles.

ewg118 commented 11 years ago

I'll take a look. The CSV download script hasn't been edited in years, so no doubt there are improvements that can be made.

On Fri, Oct 25, 2013 at 3:56 PM, RomanCoins notifications@github.comwrote:

Hi Ethan, trying to workout around the available weights in a sample of our database. When I sort results in Mantis 2, for instance by year, it works fine. Then when you download the data using CSV, it does not affect the order in the database. It actually provides the user with the same order, irrespective of the way you did sort the data out.

This is obviously something one can address once he managed to convert the CSV into Excel, but this is not that straightforward a process. Is there a way the sorting functions would affect the CSV downloads? Thanks. Gilles.

— Reply to this email directly or view it on GitHubhttps://github.com/ewg118/numishare/issues/14 .

RomanCoins commented 11 years ago

Thanks. What I am doing involves downloading sections of the database, based on a start year. The issue there is that you quickly get over the 500 lines limit. There is even a single year in the Greek Department that gets over the limit - AD 244 provides you with 1,094 coins. Is there a way to go around that limit? Next question, when you play with different date range, there is no way to correct them as you move on. Each time, you need to go back to the welcome screen or open a new browser, which becomes quite tedious once you have extracted 10 different ranges. Could we keep the date range entry field into the Refine Results fields once you have got your initial result and wishes to amend it? Cheers. Gilles.

ewg118 commented 11 years ago

I have increased the limit to 1000, but I hesitate to increase the limit beyond that because of how taxing it might be to the server. The sort parameter is now passed into the CSV, so the CSV file will now be in the same order reflected by the search results page.

RomanCoins commented 11 years ago

many thanks!

From: Ethan Gruber notifications@github.com To: ewg118/numishare numishare@noreply.github.com Cc: RomanCoins bransbourg@btinternet.com Sent: Monday, 28 October 2013, 9:37 Subject: Re: [numishare] Mantis - database extraction related issues (#14)

I have increased the limit to 1000, but I hesitate to increase the limit beyond that because of how taxing it might be to the server. The sort parameter is now passed into the CSV, so the CSV file will now be in the same order reflected by the search results page. — Reply to this email directly or view it on GitHub.

ewg118 commented 11 years ago

I have implemented the date range on the browse page, so now it should be easier to do range searches without reloading the page.

RomanCoins commented 11 years ago

Wonderful, many thanks again!

From: Ethan Gruber notifications@github.com To: ewg118/numishare numishare@noreply.github.com Cc: RomanCoins bransbourg@btinternet.com Sent: Monday, 28 October 2013, 10:02 Subject: Re: [numishare] Mantis - database extraction related issues (#14)

I have implemented the date range on the browse page, so now it should be easier to do range searches without reloading the page. — Reply to this email directly or view it on GitHub.