bibdesk-develop Mailing List for BibDesk

Sure. BibDesk is open source, and most of the defaults are just the behavior of the standard bibtex styles.

The default types and fields are in the TypeInfo.plist file in the project and the app bundle.

Christiaan

> On 13 Jan 2023, at 01:31, Emiliano Heyns <emi...@ir...> wrote:
> 
> Clear. Would it be OK for me to take the defaults of these prefs into my project? If so, where can I find these?
> 
> On Fri, 13 Jan 2023 at 01:28, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote:
> 
> 
>> On 13 Jan 2023, at 01:20, Emiliano Heyns <emi...@ir... <mailto:emi...@ir...>> wrote:
>> 
>> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
>> On Fri, 13 Jan 2023 at 00:50, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote:
>> 
>> I am not completely clear about the question. For one thing, the item you mentions just has a booktitle field, so the crossref does not seem relevant for it.
>> 
>> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
>> 
>>  <>
>> This is more compact sample:
>> 
>> @inproceedings{author:06,
>>   title = {Some publication title},
>>   author = {Author, First and Author, Second},
>>   crossref = {conference:06},
>>   pages = {330—331}
>> }
>> @book{conference:06,
>>   editor = {Editor, First and Editor, Second},
>>   title = {Proceedings of the Xth Conference on XYZ},
>>   booktitle = {Proceedings of the Xth Conference on XYZ (Book)},
>>   year = {2006},
>>   month = {oct}
>> }
>> 
>>  <>
>>  
>> Are you talking about the tex preview?
>> 
>> I'm not sure -- when I click an item in bibdesk, there's a preview below the list, is that what you mean? If so, then yes -- that preview of author:06 shows a booktitle, and if I double-click author:06, it shows the booktitle in grey, with an arrow to open the parent item. Somewhere bibdesk must know what fields are candidate for inheritance, and what they are mapped to. 
> 
> We just fill in the missing fields from the crossref item, whenever there is a crossref field. As for which fields we display, it is all required, optional, and default fields (as well as other fields that are set in the item itself). Required and optional fields depend on the type (set in the advanced Field preferences), and the default fields are the ones flagged as default in the table in the Field preferences. So in your example, the booktitle is shown as an inherited field because it is a required field for inproceedings.
> 
> Christiaan

Clear. Would it be OK for me to take the defaults of these prefs into my
project? If so, where can I find these?

On Fri, 13 Jan 2023 at 01:28, Christiaan Hofman <cmh...@gm...> wrote:

>
>
> On 13 Jan 2023, at 01:20, Emiliano Heyns <emi...@ir...>
> wrote:
>
> My bad -- the booktitle should have been inherited, not present in the @incollection
> entry.
>
> On Fri, 13 Jan 2023 at 00:50, Christiaan Hofman <cmh...@gm...>
> wrote:
>
>>
>> I am not completely clear about the question. For one thing, the item you
>> mentions just has a booktitle field, so the crossref does not seem relevant
>> for it.
>>
>
> My bad -- the booktitle should have been inherited, not present in the @incollection
> entry.
>
> This is more compact sample:
>
> @inproceedings{author:06,
>   title = {Some publication title},
>   author = {Author, First and Author, Second},
>   crossref = {conference:06},
>   pages = {330—331}
> }
> @book{conference:06,
>   editor = {Editor, First and Editor, Second},
>   title = {Proceedings of the Xth Conference on XYZ},
>   booktitle = {Proceedings of the Xth Conference on XYZ (Book)},
>   year = {2006},
>   month = {oct}
> }
>
>
>
>> Are you talking about the tex preview?
>>
>
> I'm not sure -- when I click an item in bibdesk, there's a preview below
> the list, is that what you mean? If so, then yes -- that preview of
> author:06 shows a booktitle, and if I double-click author:06, it shows the
> booktitle in grey, with an arrow to open the parent item. Somewhere bibdesk
> must know what fields are candidate for inheritance, and what they are
> mapped to.
>
>
> We just fill in the missing fields from the crossref item, whenever there
> is a crossref field. As for which fields we display, it is all required,
> optional, and default fields (as well as other fields that are set in the
> item itself). Required and optional fields depend on the type (set in the
> advanced Field preferences), and the default fields are the ones flagged as
> default in the table in the Field preferences. So in your example, the
> booktitle is shown as an inherited field because it is a required field for
> inproceedings.
>
> Christiaan
>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
>

> On 13 Jan 2023, at 01:20, Emiliano Heyns <emi...@ir...> wrote:
> 
> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
> On Fri, 13 Jan 2023 at 00:50, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote:
> 
> I am not completely clear about the question. For one thing, the item you mentions just has a booktitle field, so the crossref does not seem relevant for it.
> 
> My bad -- the booktitle should have been inherited, not present in the @incollection entry. <>
> 
>  <>
> This is more compact sample:
> 
> @inproceedings{author:06,
>   title = {Some publication title},
>   author = {Author, First and Author, Second},
>   crossref = {conference:06},
>   pages = {330—331}
> }
> @book{conference:06,
>   editor = {Editor, First and Editor, Second},
>   title = {Proceedings of the Xth Conference on XYZ},
>   booktitle = {Proceedings of the Xth Conference on XYZ (Book)},
>   year = {2006},
>   month = {oct}
> }
> 
>  <>
>  
> Are you talking about the tex preview?
> 
> I'm not sure -- when I click an item in bibdesk, there's a preview below the list, is that what you mean? If so, then yes -- that preview of author:06 shows a booktitle, and if I double-click author:06, it shows the booktitle in grey, with an arrow to open the parent item. Somewhere bibdesk must know what fields are candidate for inheritance, and what they are mapped to. 

We just fill in the missing fields from the crossref item, whenever there is a crossref field. As for which fields we display, it is all required, optional, and default fields (as well as other fields that are set in the item itself). Required and optional fields depend on the type (set in the advanced Field preferences), and the default fields are the ones flagged as default in the table in the Field preferences. So in your example, the booktitle is shown as an inherited field because it is a required field for inproceedings.

Christiaan

My bad -- the booktitle should have been inherited, not present in the
@incollection
entry.

On Fri, 13 Jan 2023 at 00:50, Christiaan Hofman <cmh...@gm...> wrote:

>
> I am not completely clear about the question. For one thing, the item you
> mentions just has a booktitle field, so the crossref does not seem relevant
> for it.
>

My bad -- the booktitle should have been inherited, not present in the
@incollection
entry.

This is more compact sample:

@inproceedings{author:06,
  title = {Some publication title},
  author = {Author, First and Author, Second},
  crossref = {conference:06},
  pages = {330—331}
}
@book{conference:06,
  editor = {Editor, First and Editor, Second},
  title = {Proceedings of the Xth Conference on XYZ},
  booktitle = {Proceedings of the Xth Conference on XYZ (Book)},
  year = {2006},
  month = {oct}
}



> Are you talking about the tex preview?
>

I'm not sure -- when I click an item in bibdesk, there's a preview below
the list, is that what you mean? If so, then yes -- that preview of
author:06 shows a booktitle, and if I double-click author:06, it shows the
booktitle in grey, with an arrow to open the parent item. Somewhere bibdesk
must know what fields are candidate for inheritance, and what they are
mapped to.

> On 12 Jan 2023, at 23:52, Emiliano Heyns <emi...@ir...> wrote:
> 
> Hi,
> 
> I'm trying to convert some bibdesk files that use crossref in a javascript bibtex parser I write, but I can't find the crossref rules that Bibdesk uses, eg to map fields from book to incollection from eg this sample:
> 
> @incollection{El-HusseiniToeplerSalamon:2004-incollection,
> 	author = {Hashem El-Husseini and Stefan Toepler and Lester M. Salamon},
> 	booktitle = {Global Civil Society: Dimensions of the Nonprofit Sector},
> 	chapter = {12},
> 	crossref = {SalamonSokolowski:2004},
> 	pages = {227--32},
> 	title = {Lebanon}}
> 
> @book{SalamonSokolowski:2004,
> 	address = {Bloomfield, CT},
> 	editor = {Lester M. Salamon and S. Wojciech Sokolowski},
> 	publisher = {Kumarian Press},
> 	title = {Global Civil Society: Dimensions of the Nonprofit Sector111},
> 	volume = {2},
> 	year = {2004}}
> bibdesk knows how to display the booktitle when viewing El-HusseiniToeplerSalamon:2004-incollection, but I can't find in the bibdesk source where that relationship is defined. Pointers would be appreciated.
> 
> Regards,
> Emiliano Heyns

I am not completely clear about the question. For one thing, the item you mentions just has a booktitle field, so the crossref does not seem relevant for it.

Are you talking about the tex preview? In  that case this is a question about bibtex, and the bibtex style you are using, not so much about BibDesk. In BibDesk we just insert the value for a field from the cross reffed item in the item that has a crossref field. 

Christiaan

Hi,

I'm trying to convert some bibdesk files that use crossref in a javascript
bibtex parser I write, but I can't find the crossref rules that Bibdesk
uses, eg to map fields from book to incollection from eg this sample:

@incollection{El-HusseiniToeplerSalamon:2004-incollection,
	author = {Hashem El-Husseini and Stefan Toepler and Lester M. Salamon},
	booktitle = {Global Civil Society: Dimensions of the Nonprofit Sector},
	chapter = {12},
	crossref = {SalamonSokolowski:2004},
	pages = {227--32},
	title = {Lebanon}}

@book{SalamonSokolowski:2004,
	address = {Bloomfield, CT},
	editor = {Lester M. Salamon and S. Wojciech Sokolowski},
	publisher = {Kumarian Press},
	title = {Global Civil Society: Dimensions of the Nonprofit Sector111},
	volume = {2},
	year = {2004}}

bibdesk knows how to display the booktitle when viewing
El-HusseiniToeplerSalamon:2004-incollection, but I can't find in the
bibdesk source where that relationship is defined. Pointers would be
appreciated.


Regards,

Emiliano Heyns

Nightly builds are down while I figure out if I can move them to another computer here. Dropbox stopped supporting the OS on my ancient laptop.

> On Feb 12, 2022, at 01:27 , Christiaan Hofman <cmh...@gm...> wrote:
> 
> 
> Do you still have this problem? There does not seem be a problem with the server ATM.

Yeah, there's something screwy with that machine, as it works fine on my other laptop. I'll try installing a new svn client. I put a new drive in last month and assumed things were running fine until I noticed Dropbox didn't have anything recent.

> On 10 Feb 2022, at 10:33, Christiaan Hofman <cmh...@gm...> wrote:
> 
> 
> 
>> On 10 Feb 2022, at 06:52, Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>> wrote:
>> 
>> Anyone else having problems with svn+ssh? This is from the nightly build log file. Helpfully, there is no -q option in my ~/.subversion/config file. I swear I've seen this before, but have no recollection of how I fixed it.
>> 
>> Updating '.':
>> svn: E170013: Unable to connect to a repository at URL 'svn+ssh://ama...@sv.../p/bibdesk/svn/trunk/bibdesk <svn+ssh://ama...@sv.../p/bibdesk/svn/trunk/bibdesk>'
>> svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
>> svn: E210002: Network connection closed unexpectedly
> 
> 
> No, it is working for me. But I have seen this several times in the past, it usually was a problem with the server that they fixed.
> 
> Christiaan
> 


Do you still have this problem? There does not seem be a problem with the server ATM.

Christiaan

> On 10 Feb 2022, at 06:52, Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote:
> 
> Anyone else having problems with svn+ssh? This is from the nightly build log file. Helpfully, there is no -q option in my ~/.subversion/config file. I swear I've seen this before, but have no recollection of how I fixed it.
> 
> Updating '.':
> svn: E170013: Unable to connect to a repository at URL 'svn+ssh://ama...@sv.../p/bibdesk/svn/trunk/bibdesk'
> svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
> svn: E210002: Network connection closed unexpectedly


No, it is working for me. But I have seen this several times in the past, it usually was a problem with the server that they fixed.

Christiaan

Anyone else having problems with svn+ssh? This is from the nightly build log file. Helpfully, there is no -q option in my ~/.subversion/config file. I swear I've seen this before, but have no recollection of how I fixed it.

Updating '.':
svn: E170013: Unable to connect to a repository at URL 'svn+ssh://ama...@sv.../p/bibdesk/svn/trunk/bibdesk'
svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: E210002: Network connection closed unexpectedly

It gets the text at the beginning and looks for certain identifiers (like DOI or PMID) using regexes.If it finds one, it fetches bibliographic info from the appropriate source.

Christiaan

> On 6 Jan 2022, at 16:36, Brian Helenbrook <bhe...@cl...> wrote:
> 
> I didn’t know it did that.  What is the requirement for this to work?  I tried a bunch of pdf files and only one of the 4 files I tried worked.  
> 
> My script converts the front page of the pdf to html and then basically finds the text with the largest font size (with some other logic) and assumes that is the title.  It then uses google scholar to grab the bibliographic information based on the title.  As long as the file is not so old that it is a bitmap, it is pretty reliable. 
> 
> Brian
> 
> 
> 
>> On Jan 6, 2022, at 10:03 AM, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote:
>> 
>> 
>> 
>>> On 5 Dec 2021, at 20:17, Arrigo Benedetti <arr...@gm... <mailto:arr...@gm...>> wrote:
>>> 
>>> Brian,
>>> 
>>> Is yours an AppleScript script? I think I want to do the same thing that your script does but since I do not know AppleScript I was planning to create a python script that generates the .bib file. Is your script available to the community?
>>> 
>>> Thanks,
>>> 
>>> -Arrigo
>>> 
>>> On Sun, Dec 5, 2021 at 11:07 AM Brian Helenbrook <bhe...@cl... <mailto:bhe...@cl...>> wrote:
>>> I’m not sure exactly what you are trying to do, but I have a script that imports a folder of pdf files then grabs the bibliographic information from google scholar for each file 
>>> 
>>>> Le 3 déc. 2021 à 4:53 PM, Arrigo Benedetti <arr...@gm... <mailto:arr...@gm...>> a écrit :
>>>> 
>>>> 
>>>> I want to write a python script that will process a large number of PDF files, extract the relevant information like DOI, etc and create a bibtex archive so I can use BibDesk. I understand that the path to the PDF is stored in the bdsk-file-1 and I was able to decode it with the python code discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/ <https://inkdroid.org/2020/09/03/bibdesk-and-zotero/>
>>>> The decoded plist has the field: 'relativePath', 'aliasData' where relativePath is obviously the relative path to the PDF file. I'm wondering if I should create the aliasData field and what should I put there. I hope that it's clear what I want to do: to create a bibtex file that BibDesk will be able to read and work on starting from a large number of PDF files. I see this for the most part a one time operation just to avoid the manual creation of thousands of entries with BibDesk. I'm planning to post the code to github when this project is completed.
>>>> 
>>>> Thanks much,
>>>> 
>>>> -Arrigo
>>>>  
>> 
>> I don’t know if you got any further with this. But perhaps you may want to know that BibDesk already tries to get DOIs and such to generate bibliographic informations for PDFs added to the database by default, for instance by dropping them on the main table. This should also happen when you add files using the AppleScript ‘import’ command. Will that give you the information that you want?
>> 
>> Christiaan

I didn’t know it did that.  What is the requirement for this to work?  I tried a bunch of pdf files and only one of the 4 files I tried worked.  

My script converts the front page of the pdf to html and then basically finds the text with the largest font size (with some other logic) and assumes that is the title.  It then uses google scholar to grab the bibliographic information based on the title.  As long as the file is not so old that it is a bitmap, it is pretty reliable. 

Brian



> On Jan 6, 2022, at 10:03 AM, Christiaan Hofman <cmh...@gm...> wrote:
> 
> 
> 
>> On 5 Dec 2021, at 20:17, Arrigo Benedetti <arr...@gm... <mailto:arr...@gm...>> wrote:
>> 
>> Brian,
>> 
>> Is yours an AppleScript script? I think I want to do the same thing that your script does but since I do not know AppleScript I was planning to create a python script that generates the .bib file. Is your script available to the community?
>> 
>> Thanks,
>> 
>> -Arrigo
>> 
>> On Sun, Dec 5, 2021 at 11:07 AM Brian Helenbrook <bhe...@cl... <mailto:bhe...@cl...>> wrote:
>> I’m not sure exactly what you are trying to do, but I have a script that imports a folder of pdf files then grabs the bibliographic information from google scholar for each file 
>> 
>>> Le 3 déc. 2021 à 4:53 PM, Arrigo Benedetti <arr...@gm... <mailto:arr...@gm...>> a écrit :
>>> 
>>> 
>>> I want to write a python script that will process a large number of PDF files, extract the relevant information like DOI, etc and create a bibtex archive so I can use BibDesk. I understand that the path to the PDF is stored in the bdsk-file-1 and I was able to decode it with the python code discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/ <https://inkdroid.org/2020/09/03/bibdesk-and-zotero/>
>>> The decoded plist has the field: 'relativePath', 'aliasData' where relativePath is obviously the relative path to the PDF file. I'm wondering if I should create the aliasData field and what should I put there. I hope that it's clear what I want to do: to create a bibtex file that BibDesk will be able to read and work on starting from a large number of PDF files. I see this for the most part a one time operation just to avoid the manual creation of thousands of entries with BibDesk. I'm planning to post the code to github when this project is completed.
>>> 
>>> Thanks much,
>>> 
>>> -Arrigo
>>>  
> 
> I don’t know if you got any further with this. But perhaps you may want to know that BibDesk already tries to get DOIs and such to generate bibliographic informations for PDFs added to the database by default, for instance by dropping them on the main table. This should also happen when you add files using the AppleScript ‘import’ command. Will that give you the information that you want?
> 
> Christiaan
> 
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

> On 5 Dec 2021, at 20:17, Arrigo Benedetti <arr...@gm...> wrote:
> 
> Brian,
> 
> Is yours an AppleScript script? I think I want to do the same thing that your script does but since I do not know AppleScript I was planning to create a python script that generates the .bib file. Is your script available to the community?
> 
> Thanks,
> 
> -Arrigo
> 
> On Sun, Dec 5, 2021 at 11:07 AM Brian Helenbrook <bhe...@cl... <mailto:bhe...@cl...>> wrote:
> I’m not sure exactly what you are trying to do, but I have a script that imports a folder of pdf files then grabs the bibliographic information from google scholar for each file 
> 
>> Le 3 déc. 2021 à 4:53 PM, Arrigo Benedetti <arr...@gm... <mailto:arr...@gm...>> a écrit :
>> 
>> 
>> I want to write a python script that will process a large number of PDF files, extract the relevant information like DOI, etc and create a bibtex archive so I can use BibDesk. I understand that the path to the PDF is stored in the bdsk-file-1 and I was able to decode it with the python code discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/ <https://inkdroid.org/2020/09/03/bibdesk-and-zotero/>
>> The decoded plist has the field: 'relativePath', 'aliasData' where relativePath is obviously the relative path to the PDF file. I'm wondering if I should create the aliasData field and what should I put there. I hope that it's clear what I want to do: to create a bibtex file that BibDesk will be able to read and work on starting from a large number of PDF files. I see this for the most part a one time operation just to avoid the manual creation of thousands of entries with BibDesk. I'm planning to post the code to github when this project is completed.
>> 
>> Thanks much,
>> 
>> -Arrigo
>>  

I don’t know if you got any further with this. But perhaps you may want to know that BibDesk already tries to get DOIs and such to generate bibliographic informations for PDFs added to the database by default, for instance by dropping them on the main table. This should also happen when you add files using the AppleScript ‘import’ command. Will that give you the information that you want?

Christiaan

Brian,

Is yours an AppleScript script? I think I want to do the same thing that
your script does but since I do not know AppleScript I was planning to
create a python script that generates the .bib file. Is your script
available to the community?

Thanks,

-Arrigo

On Sun, Dec 5, 2021 at 11:07 AM Brian Helenbrook <bhe...@cl...>
wrote:

> I’m not sure exactly what you are trying to do, but I have a script that
> imports a folder of pdf files then grabs the bibliographic information from
> google scholar for each file
>
> Le 3 déc. 2021 à 4:53 PM, Arrigo Benedetti <arr...@gm...> a
> écrit :
>
> 
> I want to write a python script that will process a large number of PDF
> files, extract the relevant information like DOI, etc and create a bibtex
> archive so I can use BibDesk. I understand that the path to the PDF is
> stored in the bdsk-file-1 and I was able to decode it with the python code
> discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/
> The decoded plist has the field: 'relativePath', 'aliasData' where
> relativePath is obviously the relative path to the PDF file. I'm wondering
> if I should create the aliasData field and what should I put there. I hope
> that it's clear what I want to do: to create a bibtex file that BibDesk
> will be able to read and work on starting from a large number of PDF files.
> I see this for the most part a one time operation just to avoid the manual
> creation of thousands of entries with BibDesk. I'm planning to post the
> code to github when this project is completed.
>
> Thanks much,
>
> -Arrigo
>
>
>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
>

I’m not sure exactly what you are trying to do, but I have a script that imports a folder of pdf files then grabs the bibliographic information from google scholar for each file 

> Le 3 déc. 2021 à 4:53 PM, Arrigo Benedetti <arr...@gm...> a écrit :
> 
> 
> I want to write a python script that will process a large number of PDF files, extract the relevant information like DOI, etc and create a bibtex archive so I can use BibDesk. I understand that the path to the PDF is stored in the bdsk-file-1 and I was able to decode it with the python code discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/
> The decoded plist has the field: 'relativePath', 'aliasData' where relativePath is obviously the relative path to the PDF file. I'm wondering if I should create the aliasData field and what should I put there. I hope that it's clear what I want to do: to create a bibtex file that BibDesk will be able to read and work on starting from a large number of PDF files. I see this for the most part a one time operation just to avoid the manual creation of thousands of entries with BibDesk. I'm planning to post the code to github when this project is completed.
> 
> Thanks much,
> 
> -Arrigo
>  
> 
>  
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

> On 3 Dec 2021, at 22:52, Arrigo Benedetti <arr...@gm...> wrote:
> 
> I want to write a python script that will process a large number of PDF files, extract the relevant information like DOI, etc and create a bibtex archive so I can use BibDesk. I understand that the path to the PDF is stored in the bdsk-file-1 and I was able to decode it with the python code discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/ <https://inkdroid.org/2020/09/03/bibdesk-and-zotero/>
> The decoded plist has the field: 'relativePath', 'aliasData' where relativePath is obviously the relative path to the PDF file. I'm wondering if I should create the aliasData field and what should I put there. I hope that it's clear what I want to do: to create a bibtex file that BibDesk will be able to read and work on starting from a large number of PDF files. I see this for the most part a one time operation just to avoid the manual creation of thousands of entries with BibDesk. I'm planning to post the code to github when this project is completed.
> 
> Thanks much,
> 
> -Arrigo
>  

The aliasData is data created from an AliasHandle. You can only create that using (deprecated) Core Services functions. I have no idea how data is stored there, Apple has never released the specs for it. BibDesk is open source, so you can just look into the code to see how the data is generated. This is done in the BDSKLinkedFile class. BTW, as AliasHandle is deprecated, we might in the future replace it with bookmark data. Whose format is also not documented by Apple, but it can be created using non deprecated Objective-C methods, which should also be available through the python ObjC bridge. Support for reading (and writing) this data is already present in BibDesk.

Christiaan

I want to write a python script that will process a large number of PDF
files, extract the relevant information like DOI, etc and create a bibtex
archive so I can use BibDesk. I understand that the path to the PDF is
stored in the bdsk-file-1 and I was able to decode it with the python code
discussed at https://inkdroid.org/2020/09/03/bibdesk-and-zotero/
The decoded plist has the field: 'relativePath', 'aliasData' where
relativePath is obviously the relative path to the PDF file. I'm wondering
if I should create the aliasData field and what should I put there. I hope
that it's clear what I want to do: to create a bibtex file that BibDesk
will be able to read and work on starting from a large number of PDF files.
I see this for the most part a one time operation just to avoid the manual
creation of thousands of entries with BibDesk. I'm planning to post the
code to github when this project is completed.

Thanks much,

-Arrigo

Hi Christiaan,

Just so you know, the wiki page with applescripts is kind of a mess.  I tried a few of the links and a lot didn’t work.  I will post my stuff there though.  I had old stuff there that I didn’t even remember.

Brian






> On Jun 2, 2021, at 4:39 AM, Christiaan Hofman <cmh...@gm...> wrote:
> 
> You could link it on the Wiki.
> 
> Christiaan 
> 
> Op wo 2 jun. 2021 02:48 schreef Brian Helenbrook <bhe...@cl... <mailto:bhe...@cl...>>:
> BibDesk Team,
> 
> I wrote a script and a shell utility that will extract the title from a journal pdf, then download the bibliographic data for that title from GoogleScholar.  I use it to import full folders of pdf’s sent to me by collaborators or for individual files.  Other than files that are so old that they are scans and contain no text, it has been working pretty reliably for me.  I think it would be a nice addition to BibDesk.  If I give you all of my scripts, would you be interested in including it in the project?  
> 
> Brian
> 
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li... <mailto:Bib...@li...>
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop <https://lists.sourceforge.net/lists/listinfo/bibdesk-develop>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

You could link it on the Wiki.

Christiaan

Op wo 2 jun. 2021 02:48 schreef Brian Helenbrook <bhe...@cl...>:

> BibDesk Team,
>
> I wrote a script and a shell utility that will extract the title from a
> journal pdf, then download the bibliographic data for that title from
> GoogleScholar.  I use it to import full folders of pdf’s sent to me by
> collaborators or for individual files.  Other than files that are so old
> that they are scans and contain no text, it has been working pretty
> reliably for me.  I think it would be a nice addition to BibDesk.  If I
> give you all of my scripts, would you be interested in including it in the
> project?
>
> Brian
>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
>

BibDesk Team,

I wrote a script and a shell utility that will extract the title from a journal pdf, then download the bibliographic data for that title from GoogleScholar.  I use it to import full folders of pdf’s sent to me by collaborators or for individual files.  Other than files that are so old that they are scans and contain no text, it has been working pretty reliably for me.  I think it would be a nice addition to BibDesk.  If I give you all of my scripts, would you be interested in including it in the project?  

Brian

Great news! Thanks! :)

On Sun, Jan 10, 2021 at 12:51 AM Christiaan Hofman <cmh...@gm...> wrote:
>
>
>
> On 9 Jan 2021, at 15:21, Max Kotik <sup...@gm...> wrote:
>
> Hello!  I'm an avid Zotero user, but recently I started using BibDesk
> for some of my work, and... this program feels so great!  A beautiful
> native app for macOS, just a pure gem!  So now I'm wondering if I
> should switch to BibDesk because I really like the way it works.  But
> I'm a little worried about its future: are you going to make a native
> version for Apple's new processor?  It would be so great :)
>
>
> The current source already supports this, and the next release will have it. Probably very soon!
>
> Christiaan
>
> _______________________________________________
> Bibdesk-develop mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

> On 9 Jan 2021, at 15:21, Max Kotik <sup...@gm...> wrote:
> 
> Hello!  I'm an avid Zotero user, but recently I started using BibDesk
> for some of my work, and... this program feels so great!  A beautiful
> native app for macOS, just a pure gem!  So now I'm wondering if I
> should switch to BibDesk because I really like the way it works.  But
> I'm a little worried about its future: are you going to make a native
> version for Apple's new processor?  It would be so great :)


The current source already supports this, and the next release will have it. Probably very soon!

Christiaan

Hello!  I'm an avid Zotero user, but recently I started using BibDesk
for some of my work, and... this program feels so great!  A beautiful
native app for macOS, just a pure gem!  So now I'm wondering if I
should switch to BibDesk because I really like the way it works.  But
I'm a little worried about its future: are you going to make a native
version for Apple's new processor?  It would be so great :)

Hi all,

We should resist to become all “slaves" of Apple by giving in. As long as Apple does not deprecate the mechanism to override these warnings I opt for the approach Christiaan is in favor of.

Unfortunately the open source community manages not to bombard Apple with complains that the mechanism to override this blocking of all not Apple Store software is not offered by default. But in my view that is the approach we should go for, not the opposite. Otherwise we risk to harm open source developments in general, I fear.

Regards,
Andreas


ETH Zurich
Prof. em. Dr. Andreas Fischlin
IPCC Vice-Chair WGII
Systems Ecology - Institute of Biogeochemistry and Pollutant Dynamics
CHN E 24
Universitaetstrasse 16
8092 Zurich
SWITZERLAND

and...@en...<mailto:and...@en...>
www.sysecol.ethz.ch/people/andreas.fischlin.hml<http://www.sysecol.ethz.ch/people/andreas.fischlin.hml>

+41 44 633-6090 phone
+41 44 633-1136 fax
+41 79 595-4050 mobile

             Make it as simple as possible, but distrust it!
________________________________________________________________________








On 14/11/2020, at 14:48, Hein Meling <hei...@gm...<mailto:hei...@gm...>> wrote:

Hi,

I wasn’t planning to use BibDesk at the moment, so this isn’t urgent for my part. However, after upgrading to macOS Big Sur, I was once again notified that the app needs to be updated… (see attached screenshot). I can of course disable this check and run it anyway, but why not put this through the Apple process and get it checked and signed.

At the same time, I’m curious why still stay on sourceforge? It feels so antiquated and full of commercials that I’d rather stay away from it… I personally use GitHub, but there are others like bitbucket and gitlab. While I’m not a macOS dev, I suspect that it would be easier to get help from others if hosted on github.

Best,
:) Hein


<Screen Shot 2020-11-14 at 14.26.51.png>
_______________________________________________
Bibdesk-develop mailing list
Bib...@li...<mailto:Bib...@li...>
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop