Dear Kelly, the bistreams like you said are joined to the items throught bundles. The relation is:
bitstreams---bundle----item between these relation are the intermidate table item2bundle and bundle2bitstreams. The path of the file is saved in the field internal_id and it saved in the folder that you installed in the folder assetstore. For example the bitstream with internal_id as 164410876697102632819538106564350084233 is saved in dspace/assetstore/16/44/10/164410876697102632819538106564350084233 The bistreams also has metadata. In this metadata you can find data as title,source and others. Best Regard Gianpierre Calderon, UNMSM, PERU (+51)941607813 El mié, 12 jun 2024 a las 16:31, Kelley Canon (<kelley_ca...@sil.org>) escribió: > Thanks, Mark. > > Kelley Canon > *Generations will REAP what we sow!* > *Find REAP & RAMP help and LCA info on Gateway > <https://gateway.sil.org/pages/viewpage.action?spaceKey=REAP&title=Language+and+Culture+Archives>* > Language & Culture Archives - REAP Administrator > SIL International > > > On Mon, Jun 10, 2024 at 1:01 PM <mw...@iu.edu> wrote: > >> On Fri, Jun 07, 2024 at 09:36:37PM +0000, Kelley Canon wrote: >> > You don't often get email from kelley_ca...@sil.org. Learn why this is >> important<https://aka.ms/LearnAboutSenderIdentification> >> > Tiim - >> > >> > Thanks for your reply. >> > >> > Interesting. And a bit frustrating. It would be nice if this were >> mentioned in documentation, especially when there are other tables with >> "Bitstream" in the name that DO contain most of the information you'd want >> about bitstreams. bitstream_id, checksum, size, etc. >> > >> > Water under the bridge I guess! >> > >> > I do wonder, however, how do we distinguish bitstream data in the >> metadatavalue table - in dc.title - from true item titles? >> >> One way would be to join the metadatavalue and bitstream tables: >> >> SELECT * FROM metadatavalue AS m JOIN bitstream AS b >> ON m.dspace_object_id = b.uuid limit 1; >> >> >> >> -- >> Mark H. Wood >> Lead Technology Analyst >> >> University Library >> Indiana University Indianapolis >> 755 W. Michigan Street >> Indianapolis, IN 46202 >> 317-274-0749 >> library.indianapolis.iu.edu >> >> -- >> All messages to this mailing list should adhere to the Code of Conduct: >> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dspace-tech+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/Zmc8VAgwyuMiV8mV%40iu.edu. >> > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/CACXx6Fuj3FiRCEtaSRXxhuaT%2Bo3Y_5wvj%3D-wkY1GF6upqMF2_g%40mail.gmail.com > <https://groups.google.com/d/msgid/dspace-tech/CACXx6Fuj3FiRCEtaSRXxhuaT%2Bo3Y_5wvj%3D-wkY1GF6upqMF2_g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAMyCP2fUNYMKV1Un3E-NNF1VgJMPrP0rMN-sZ_QKXd-%3DqNW8Yw%40mail.gmail.com.
