I frequently find the need to export contacts I’ve collected using Evernote’s excellent business card photo feature. But the process is not as straightforward as export > csv.
The best solution I’ve found (on Mac) is saving the business cards to contacts.
This can be done automatically at the time the cards are created, or manually later from the mobile app or desktop app.
Automatically (iPhone, iPad, and iPod Touch): To save information from every card scanned, simply tap your account name and select General > Camera > Business Cards and toggle ‘Save to Contacts’ or
Manually: Select Save to contacts from the options menu (iPhone, iPad, and iPod Touch) or from the pop-up menu displayed after each completed scan (Android) (reference KB article: https://evernote.com…rticle/53057988)
From the desktop app, save each card to contacts individually, or select several cards at once to be saved to contacts.
Select Share>Save to Contacts from the individual card drop down menu, or from the main menu Note > More Sharing > Save to Contacts
These saved contacts will show up in your iCloud contacts. Unfortunately, I found no way of saving the Evernote tags with the contact in iCloud so that the saved contact could be easily identified (if someone else does, please lmk!).
From iContacts, one can export selected contacts (singularly or in bulk) using File > Export > vCard.
ZIP+4 has been in place for over THIRTY YEARS.
ZIP+4 code, introduced in 1983, includes the five digits of the ZIP code, a hyphen, and four more digits that determine a more specific location within a given ZIP code.
So WHY don’t coders implement web-forms to accommodate this thirty-year-old standard?
The developer of the webpage from which the screenshot above was taken (Diamond Mind) even specified TEN DIGITS for the zip code form field!
<input value="" name="postal_code" maxlength="10" class="dm-fb-zip-code" id="dm-fb-zip-code" type="TEXT">
Why go to the trouble of writing a validation script for a zip code field without going to the trouble of limiting the number of input characters?
More troubling, why specify 10-character maxlength for a five-digit validated field?
And check this out, the developer specified a maxlength, but didn’t bother to specify “digits only”:
Good Grief Charlie Brown.
No surprise – “that depends.” There is no legal requirement for a specific duration. The duration is completely up to the parties of the agreement.
That said, people think and work on year-based intervals. Most frequently, the durations used for non-disclosure agreements are 2, 3, and 5 years, which are the durations of the standard term used in the EasyNDA agreement.
BUT – There’s more to the NDA than duration alone: There is whether or not the agreement terminates after a predefined duration, and the “term” after proprietary information is exchanged during which confidentiality must be maintained.
Though some NDA’s automatically terminate after a specified period of time (in terminating agreements, this period of time is often referred to as the “term” of the agreement), it is not uncommon that some agreements never terminate (automatically).
This means there are two kinds of agreements:
Terminating agreements have an effective date on which the agreement starts, and a duration after which the agreement stops. In these terminating agreements, the duration of the agreement is often called the “term” of the agreement. The “term” of the agreement therefore, can refer to how long the agreement is in effect.
What can be confusing, is that the same “term” can also refer to the period of time after which proprietary information is exchanged that the receiving party’s duties of confidentiality continue – whether or not the duration of the agreement has passed.
For example, a three-year termed agreement may come to an end three years after the effective date; however, the receiving party of proprietary information exchanged on the last day of that three-year duration, or term, will CONTINUE to have a duty of confidentiality for that last exchanged information an additional three-years; again, the “term.”
Terminating agreements have a problem though. The problem comes into play with trade secrets. Trade secrets are those bits of proprietary information that never lose their value – in fact, are priceless to the owner of the trade secret (think Coca-Cola formulations). If a trade secret is disclosed under a terminating NDA, then after the term, the receiving party is no longer under a duty of confidentiality for the trade secret. Trade secret protection is one of the reasons for using non-terminating agreements.
Therefore, a term-limited NDA makes sense only for limited-life information, e.g. marketing plans which will be used by the end of the term. A terminating NDA would be an unwise choice for other types of trade secret information with longer-term value, such as recipes, processes, source code, etc. because the asset may need protection for longer than the term of the agreement.
Non-terminating agreements don’t terminate (duh) and are perpetually in effect as long as neither party takes action to terminate the agreement. Non-terminating agreements are convenient for parties that have on-going relationships.
The “term” of confidential duty for non-terminating agreements is the period of time after the disclosure of proprietary information once the agreement has been actively terminated.
For example, EasyNDA’s agreement remains in effect perpetually unless one of the parties terminates the agreement (which can be done within one business day of written notice). The term of the agreement can be set to 2, 3, or 5 years. This is the period of time after termination of the agreement that confidentiality of proprietary information exchanged must be maintained by the receiving party:
This agreement is effective as of the Effective Date specified above (the “Effective Date”) and continues until terminated by either party as provided in Section 9. Notwithstanding the termination of this Agreement, each party’s duties with respect to the other party’s Proprietary Information shall continue for [ term of the agreement ] after the time of disclosure.
And can be terminated:
Either party may terminate this Agreement at any time by giving one business day’s written notice to the other party at its address provided above, after which Recipient’s obligations to Discloser are limited to that Proprietary Information disclosed before termination,
Learn more on EasyNDA’s FAQ page.
Optimizr sent us a note.
The file-size for the HTML-document should be as small as possible.
Last month, @CBS Bay Area wrote about Silicon Valley’s Jonathan Hart (@jonathanhartsf), lead mobile engineer for Idle Games, who hacked into the Burning Man servers to snag tickets ahead of the 80,000 people waiting in line – then tweeted about it leading to some 200 more of similar morality doing the same.
Navigated @Ticketfly’s completely hosed web servers and crawled out with 2 @burningman tickets… woohooo!
— Jonathan Hart (@jonathanhartsf) February 18, 2015
Francisco Dao, a Los Angles-based Venture Beat columnist and Founder of SEAL CAMP and 50Kings, posted about the hacking of Ticketfly on Facebook. When I commented,
[the hackers] are the equivalent of looters walking through a broken window in Ticketfly’s business. – me
Francisco pointed to the “new morality” pervasive in Silicon Valley.
In the “new morality” it’s not cheating or cutting in line. It’s “hacking Burning Man!” – Francisco Dao
I’ve been using Thunderbird as my email client on my Mac because Mac Mail does not have the business and multi-account features I need. I’d use Outlook for Mac, but it will not support Google Calendar – only Exchange calendar. So Thunderbird has been the go-to solution for me.
But Thunderbird has a little problem: It can pull a Dementor on your CPU.
In my case, Thunderbird is running on a Mac Pro with 8 cores and 26GB of ram – so the problem was not system resources… it was something else. (more…)
One of our favorite things at EasyNDA is hearing from people who have lived and breathed the non-disclosure agreement “problem.”
Jim Ko is just such a person and Jim has joined EasyNDA’s advisory board.
As Jim Puts it:
“I’ve negotiated 100s of NDAs in my career, reviewing countless standard NDAs of other companies and often revising my own company’s standard NDA in a constant effort to streamline the process. I wish I had this EasyNDA Standard MNDA from the start. It’s far more simple, reasonable, and effective than any I have come across.”
Jim has already been a big help streamlining our standard non-disclosure agreement (revision published on January 9, 2014: What’s New in EasyNDA’s Non-Disclosure Agreement.
Today we published a release that improves the terms of our mutual non-disclosure agreement (MNDA). As a service to our subscribers, we frequently review our standard NDA to ensure we provide a document that should meet the needs of equitable confidentiality agreements. As always, have your attorney review EasyNDA’s MNDA to ensure it’s suitable to your needs.
These are the revisions made to our MDNA in this release:
So did I after installing OSX Yosemite.
Turns out that OSX Yosemite changes the sound of feedback when changing volume levels on your Mac and defaults the change to not play the feedback.
Simple fix if you still want feedback when changing audio levels.
Open System Preferences (lots of ways to do this, including using Spotlight search).
Then, in the bottom third of the window, locate the check box for “Play feedback when volume is changed” and make your selection:
That’s all there is to it!
Two entities get together and agree not to reveal what they share between them with anyone else. Oh, and they agree not to share this information with anyone else for a specific period of time, called the “term” of the agreement.
Common “terms” are 2, 3, and 5 years.
From the date of termination of the agreement.