This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n3http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n6http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:PtN8rS9064S9DzxpnKCuEg
rdf:type
rev:Review
schema:dateCreated
2014-08-15T00:00:00
schema:itemReviewed
n6:szdXCAagDGX4kA7EPZ0kEw
n3:funnyReviews
9
rev:rating
2
n3:usefulReviews
7
rev:text
Morons! I'm not going to put the officer on blast who completely screwed up what should have been a simple deposit because mayyyyybe she was having a bad day. Have been a customer for more than a decade and maintain a variety of accounts with NSB. Recently deposited a sizable local check which was easily verifiable. Explained to the officer that I needed a certain amount available (not even 1/10 of check amount) right away; assured this was no problem. Through a Murphy's Law chain of events, the funds were not available for THREE DAYS and a third party who agreed to hold a check I wrote them deposited it too soon thus my overdraft line kicked in. So, when I went back to the branch to discuss the matter, the other staff told me this officer was busy (I could SEE her in the back) Anyway, it pissed me off. Quite a bit. Enough that when some investments mature, I'm switching banks. Fund availability is not rocket science, and quite honestly the whole amount should have been available, but I didn't need it. The only explanation I received - without apology - was "it takes 24 hours for our system to update" ummm, horseshit! Cya, NSB...
n3:coolReviews
6
rev:reviewer
n7:eZfHm0qI8A_HfvXScwIYsg