Dear Franco, many thanks for your suggestion! We do currently use this construct to represent the format of the book (folio, quarto, etc.). Indeed it might be an option to use the same for sheets.
The reason I am hesitant to do so is because the number of sheets is more a property of the printing process than of the final book. Say you can print 16 pages using one print sheet and you intend to print a booklet of 20 pages. You would then require two sheets to print the booklet, ending up with 12 empty pages that will not be included in the book (apologies if this is all factually incorrect, I'm not a book historian, just illustrating the thinking behind not modelling the number of sheets as a property of the book). For this reason my thinking was that it would make more sense to add this information somewhere in the F3/E29 area. What do you think about using CLP43 should have dimension -> E54 Dimension on F3 Manifestation Product Type? Best, Florian > On 17. Apr 2020, at 13:16, Franco Niccolucci <[email protected]> > wrote: > > First thing coming to my mind, assuming for instance it is “Yourbook” of 150 > sheets: introduce an E54 Dimension "number of sheets” and measure it > > E70 Thing <“Yourbook”> (or whatever way you encode the physical book) > P43 has dimension > E54 Dimension <"Number of sheets"> > P90 has value > E60 Number <150> > P91 has unit > E58 Measurement Unit <"Sheet number"> > > A bit verbose but you can extract & process directly the number of sheets, > select small books etc., calculate the printing cost etc > Note that P43 has domain E70 Thing so you can attach it to any subclass of > Thing / physical object you wish to use for the book. E-books may require > further work/different approach. > > Obviously this refers to a specific paper edition, exactly “that" tangible > object, as a paperback may have a number of pages different from a hard-cover > of the same literary object. > > Franco > > Prof. Franco Niccolucci > Director, VAST-LAB > PIN - U. of Florence > Scientific Coordinator > ARIADNEplus - PARTHENOS > > Editor-in-Chief > ACM Journal of Computing and Cultural Heritage (JOCCH) > > Piazza Ciardi 25 > 59100 Prato, Italy > > >> Il giorno 17 apr 2020, alle ore 12:07, Florian Kräutli >> <[email protected]> ha scritto: >> >> Dear all, >> >> I have a data modelling issue that I would like to discuss with you. >> >> We have a database of books. Currently we are in the process of identifying, >> for each book, the number of sheets used to print it. The number of sheets >> is a good indication for the investment required to print a book. We want to >> store this information in the database. >> >> We do already capture the number of pages in the digitised copy as well as >> the physical format of the book (using P43 has dimension on an F5 Item). We >> capture data related to the printing of the book via a F3 Manifestation >> Product Type and a F32 Carrier Production Event. >> >> My intuition is that the number of sheets could be modelled as an E29 Design >> or Procedure that P129 is about the F3 Manifestation Product Type. >> >> But how to add the information "number of sheets" to the E29 Design? >> >> Two thoughts: >> - Simply as P3 has note: "20 sheets" (I would like it to be more machine >> readable) >> - as a P68 foresees use of E57 Material that P2 has type "sheet" (but where >> to add the quantity of sheets?) >> >> What do you think? >> >> Best wishes, >> >> Florian >> _______________________________________________ >> Crm-sig mailing list >> [email protected] >> http://lists.ics.forth.gr/mailman/listinfo/crm-sig > _______________________________________________ Crm-sig mailing list [email protected] http://lists.ics.forth.gr/mailman/listinfo/crm-sig
