This is the archive of the goodrelations dicussion list

Dear all:

Attached, please find an email from the mailing list for the MSemantic extension, which adds GoodRelations to Magento shops.

I thought this might be relevant for the subscribers of this list, too.

MSemantic is a really strong (and free) GoodRelations extension written by Uwe Stoll that gets you Google Rich Snippets and Semantic SEO within 15 minutes or so.

See also here

http://www.magentocommerce.com/magento-connect/semantium/extension/2838/semantium_msemanticbasic#overview

Best

Martin Hepp

Begin forwarded message:

> Subject: Re: Can you help me configuring this extension
> 
> Hi,
> 
> please see inline comments:
> 
>> 
>> Hello Sir
>> 
>> Please find the details given below which i entered during configration...
>> Please help me where i am wrong and some fields i don't know what to fill.
>> 
>> Basic Settings
>> --------------
>> 1. Enable -> Yes
>> 2. Semantic Web Ready Link -> No
> This controls whether the kind acknowledgment text "Semantic Web - ready thanks to <a href="http://www.msemantic.com" is being shown as a gratitude for providing the extension for free.
>> 
>> Business Information
>> --------------------
>> Legal Name -> Business name
> 
> This should hold the official name of the person or company operating the shop, e.g. "Miller Trading LLC", even if the Web shop name was "diapers-online.com".
>> 
>> Company Address
>> ---------------
>> I filled the complete address here.
>> 
> Ok
>> Point of Sale Address
>> ---------------------
>> POS Available ? => No
>> Same Pos address as company -> Yes
>> 
> These two options allow exposing information about a brick-and-mortar store associated with the online shop. If you do not have a regular store, disable "POS".
> If the address of the store is the same as the address you entered for the company, check "Yes" for "Same Pos address as company ". Otherwise specify the address of the store.
> 
>> General Offering Description
>> ----------------------------
>> Short Description - > I filled a short description about my offerings.
> Ok. This is for consumers of the data that try to find a matching shop, not a particular product.
>> 
>> 
>> Eligible types of business partners
>> -----------------------------------
>> 1. End Users -> Yes
>> 2. Business -> Yes
>> 3. Resellers -> Yes
>> 4. Public Institutions -> No
> 
> This indicates the types of audiences you are willing to sell to.
>> 
>> Payment Options
>> ---------------
>> 
>> ByBank Transfer in Advance - > No
>> By Invoice -> No
>> Cash -> No
>> Check in Advance -> No
>> COD -> No
>> Direct Debit -> No
>> Google Checkout -> Yes
>> Paypal -> Yes
>> American Express -> Yes
>> DinersClub -> Yes
>> Discover -> Yes
>> JCB-> Yes
>> Master Card -> Yes
>> VISA -> Yes
> 
> Ok if these are the payment options you accept for all items in your shop.
> 
>> 
>> Delivery Methods
>> ----------------
>> 1. DHL -> Yes
>> 2. UPS -> Yes
>> 3. AIR or surface mail -> No
>> 4. FedEx -> Yes
>> 5. Direct Download -> No
>> 6. Pick up -> No
>> 7. Vendor Fleet -> No
>> 8. Freight -> Yes
>> 
> Ok if these are the delivery options you accept for all items in your shop.
> 
> Note that if you use DHL or UPS at *your discretion* (i.e. the customer cannot choose), then it is better to check just "Freight".
> 
>> 
>> Strong Identifier
>> -----------------
>> Strong Identifier Type -> EAN_UCC_13 ( I am confuse here, What shold i enter here )
> This is typically okay - it determines the type of strong product identifier published for your items. EAN / UCC_13 / GTIN 13, ISBN13 / UPC are all names for the same identifier.
> Only if you are using GTIN8 ("short UPC/EAN") or long GTIN14 identifiers from the logistics you may want to change this option.
> 
> 
>> Use Existing Attribute -> No ( I am confuse here, What shold i enter here )
> 
> Magento has an existing attribute for product identifiers. If you check "Yes" in here, MSemantic will use that field for publishing EAN/UPC data. If you check "No", Msemantic will use a proprietary additional attribute, which you will have to maintain for each product then.
> 
>> Attribute -> Age Group -> ( I am confuse here, What shold i enter here )
>> 
> This one I have to pass to Uwe Stoll.
> 
> 
>> Validity of your statement
>> --------------------------
>> Validity Period - > 3 months
>> Valid Through -> tomorrow 
>> 
> With these options, you indicate for how long your offers and prices can be assumed to be valid. Use the longest validity period that you can promise (they can be different for price and offer), because it can be that Google disables showing a price in a rich snippet if the validity period expires before Google will have re-crawled the page with an updated validity interval.
> 
> 48 hours after the date and time of creating the page is the minimum that works well; if you can typically promise a validity of seven days from the time of the HTTP request that creates the page, that will often be better.
> 
> See also
> 
> http://ebusiness-unibw.org/pipermail/goodrelations/2011-June/000364.html
> 
> 
> Hope that helps!
> 
> Best wishes
> 
> Martin Hepp
> 
> 

--------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  hepp at ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
=================================================================
* Project Main Page: http://purl.org/goodrelations/