On 2007-August-30 , at 08:33 , Adam R. Maxwell wrote:
> On Wednesday, August 29, 2007, at 11:20PM, "jiho"
> <[EMAIL PROTECTED]> wrote:
>> On 2007-August-29 , at 20:15 , Adam R. Maxwell wrote:
>>> On Wednesday, August 29, 2007, at 10:37AM, "Chris Goedde"
>>> <[EMAIL PROTECTED]> wrote:
>>>> On Aug 29, 2007, at 12:28 PM, Adam R. Maxwell wrote:
>>>>> There would be no main file field, and you wouldn't set a field
>>>>> name/type for files in prefs. Fields would be added
>>>>> dynamically as
>>>>> needed. So you drop two files on the view, and one is assigned to
>>>>> Bdsk-File-1, and the other is Bdsk-File-2 in the BibTeX file. All
>>>>> you see is the file's name, and its icon. This assumes you're not
>>>>> already using that naming scheme for something else :). Same idea
>>>>> goes for adding files via AS.
>>>>
>>>> Now I'm a bit confused. Are you saying that BibDesk would not
>>>> rename
>>>> and relocate the pdf file? That seems like a step backward.
>>>
>>> Autofile would work as it does presently, except it would be
>>> applied to all files associated with an item, not just Local-Url.
>>> So you drop a file on the view, and if there's enough info, it's
>>> autofiled immediately. If not, we could badge it with a caution
>>> icon or something.
>>
>> What about the naming convention? I really like the fact that all my
>> PDFs are named by Author+year+title. This allows me to find pdfs via
>> spotlight/finder easily without having to run bibdesk everytime.
>> Could this system autofile several files and gives them a name
>> such as:
>> author-year-title-1.pdf
>> author-year-title-2.html
>> author-year-title-3.jpg
>> etc...
>> instead of Bdsk-file-1.pdf, Bdsk-file-2.html etc. ? It would be
>> really useful this way. Otherwise I think I would (personally) keep
>> using the old Local-Url system.
>
> It seems that many people are missing the point, so I'm likely not
> explaining this effectively. You'd have a BibTeX entry like so:
>
> @article{citekey,
> title={Something},
> author={Some One},
> year={2006},
> bdsk-file-1=
> {somelongstringofasciilettersthattranslatesintoanaliaswhenopeningthefi
> leinbibdesk},
> bdsk-file-2=
> {anotherlongstringofasciilettersthattranslateseintoanaliswhenopeningth
> efileinbibdesk}
> }
>
> but in the Finder and BibDesk the file names show up as
>
> "SomeOne-2006-Something-a.pdf"
> "SomeOne-2006-Something-b.rtf"
> "SomeOne-2006-Something-c.png"
OK, I get it. My question was then: would it still be possible to
generate those names automatically? I am wondering since you said:
"and you wouldn't set a field name/type for files in prefs"
> and the file is located in your papers directory according to your
> autofile scheme. You can then rename the file in Finder and/or
> move it to a different directory without hand-editing a field in
> BibDesk, and BibDesk will still be able to find it. You will /not/
> be able to open the BibTeX file in TextEdit and manually change the
> bdsk-file-1 field, because it's not human-readable.
JiHO
---
http://jo.irisson.free.fr/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
