Difference between revisions of "Talk:PubMan Func Spec Export"
(extended "possible solution" and commented Robert's and Natasa's comments.) |
|||
| Line 4: | Line 4: | ||
if it is for technical reasons, it should be possible to specify this limit. [[User:Robert|Robert]] 09:56, 21 December 2007 (CET) | if it is for technical reasons, it should be possible to specify this limit. [[User:Robert|Robert]] 09:56, 21 December 2007 (CET) | ||
From the functional point of view all records, the user wants to download should be | From the functional point of view all records, the user wants to download should be exported. And if only records without full texts are being exported, I think it should be possible. Giving a limit for records, that can be exported is not possible for my understanding, because the size of a record can differ. If it takes longer to export, then the user should get an information on the fact, that it takes time. Like a sandglass or something. | ||
Besisdes that, I think we should only talk on exporting records as in items, describing the metadata of a record and not the attached file, as we didn't specify functionally yet, how the export of files should look like. | Besisdes that, I think we should only talk on exporting records as in items, describing the metadata of a record and not the attached file, as we didn't specify functionally yet, how the export of files should look like. | ||
I also think, that we should not go for the alternative, suggested by Natasa, because it will cause frustration ;-) for the user. --[[User:Nicole|Nicole]] 15:13, 7 January 2008 (CET) | I also think, that we should not go for the alternative, suggested by Natasa, because it will cause frustration ;-) for the user. --[[User:Nicole|Nicole]] 15:13, 7 January 2008 (CET) | ||
Revision as of 14:52, 7 January 2008
Discussion on exporting[edit]
Problem: item export needs a reasonable limit (obergrenze) due to technical reasons. if it is for technical reasons, it should be possible to specify this limit. Robert 09:56, 21 December 2007 (CET)
From the functional point of view all records, the user wants to download should be exported. And if only records without full texts are being exported, I think it should be possible. Giving a limit for records, that can be exported is not possible for my understanding, because the size of a record can differ. If it takes longer to export, then the user should get an information on the fact, that it takes time. Like a sandglass or something. Besisdes that, I think we should only talk on exporting records as in items, describing the metadata of a record and not the attached file, as we didn't specify functionally yet, how the export of files should look like. I also think, that we should not go for the alternative, suggested by Natasa, because it will cause frustration ;-) for the user. --Nicole 15:13, 7 January 2008 (CET)
Possible solution:
- User selects items
- user chooses to export the items
- the system calculates the total sice of the export
- user gets an information on how many MB s/he wants to export
- user can decide if s/he wants to continue exporting/sending the export E-Mail or if s/he wants to deselect some items
- if it will take longer to export than a few secounds the user will get a sandglass or something so that s/he knows that it will take some time until the export is finished. This is common pratice (see e.g. WoS).
Another alternative:
- This was somewhere stated as well, i remember that Ulla and me were talking on this. However, as probably users do not really have an idea on what means "n MB" after selection of the items maybe the system may provide some "more friendly" information such as : "You have selected 1000 items, but you can export the first 150 items (number calculated by the system, depending on selections) of your selection due to limitation of the size of the export ..etc.." - and then she decides.
- Other alternative is that the system takes care if the user specified 1000 items, the system should be able to "split" in reasonable packages and send several emails as "export part 1".."export part n" :)) (But would consider that at some later stage).
--Natasa 16:45, 21 December 2007 (CET)