#786 closed defect (fixed)
Add numPages field
| Reported by: | dstillman | Owned by: | dstillman |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | data layer | Version: | 1.5 |
| Keywords: | schema-update | Cc: | erazlogo |
Description
Currently "pages" is used both for the number of total pages in a book and for the page on which an article appears.
Change History (5)
comment:1 Changed 9 years ago by erazlogo
- Cc erazlogo added
comment:2 Changed 9 years ago by dstillman
- Summary changed from Add pageRange (or numPages?) field to Add numPages field
Great--thanks.
comment:3 Changed 8 years ago by dstillman
- Keywords schema-update added
comment:4 Changed 7 years ago by dstillman
- Resolution set to fixed
- Status changed from new to closed
(In [4477]) 2.0b3 megacommit
- Support for group libraries
- General support for multiple libraries of different types
- Streamlined sync support
- Using solely libraryID and key rather than itemID, and removed all itemID-changing code
- Combined two requests for increased performance and decreased server load
- Added warning on user account change
- Provide explicit error message on SSL failure
- Removed snapshot and link toolbar buttons and changed browser context menu options and drags to create parent items + snapshots
- Closes #786, Add numPages field
- Fixes #1063, Duplicate item with tags broken in Sync Preview
- Added better purging of deleted tags
- Added local user key before first sync
- Add clientDateModified to all objects for more flexibility in syncing
- Added new triples-based Relation object type, currently used to store links between items copied between local and group libraries
- Updated zotero.org translator for groups
- Additional trigger-based consistency checks
- Fixed broken URL drag in Firefox 3.5
- Disabled zeroconf menu option (no longer functional)
Developer-specific changes:
- Overhauled data layer
- Data object constructors no longer take arguments (return to 1.0-like API)
- Existing objects can be retrieved by setting id or library/key properties
- id/library/key must be set for new objects before other fields
- New methods:
- ZoteroPane.getSelectedLibraryID()
- ZoteroPane.getSelectedGroup(asID)
- ZoteroPane.addItemFromDocument(doc, itemType, saveSnapshot)
- ZoteroPane.addItemFromURL(url, itemType)
- ZoteroPane.canEdit()
- Zotero.CollectionTreeView.selectLibrary(libraryID)
- New Zotero.URI methods
- Changed methods
- Many data object methods now take a libraryID
- ZoteroPane.addAttachmentFromPage(link, itemID)
- Removed saveItem and saveAttachments parameters from Zotero.Translate constructor
- translate() now takes a libraryID, null for local library, or false to not save items (previously on constructor)
- saveAttachments is now a translate() parameter
- Zotero.flattenArguments() better handles passed objects
- Zotero.File.getFileHash() (not currently used)
comment:5 Changed 6 years ago by dstillman
- Milestone 2.0 Beta 3 deleted
Milestone 2.0 Beta 3 deleted
Note: See
TracTickets for help on using
tickets.
In most cases, Pages field would contain page range (i.e. 12-35, etc.), which is necessary for citation--it would be great if this remained the purpose of the existing field. If you create the new field, please make it store the total number of pages--only books or, rarely, manuscripts, would have that value, and, as far as I know, it is never necessary for citation purposes.