미디어 피드는 TV 시리즈, 영화, 노래, 앨범 등 카탈로그의 미디어 콘텐츠를 나타내는 항목 모음을 포함하는 JSON 객체입니다. 온보딩 프로세스의 첫 번째 단계는 피드 개발을 시작하는 것입니다. 파일이 준비되면 Google에서 정기적으로 가져올 수 있도록 지원되는 호스팅 방법 중 하나를 사용하여 피드를 호스팅해야 합니다.
피드 파일 형식 요구사항
피드 파일의 요구사항은 다음과 같습니다.
피드 파일의 파일 이름 확장자는 .json여야 합니다.
피드 파일을 암호화하지 마세요.
피드 파일을 UTF-8로 인코딩합니다 (파일 편집기 설정 확인).
피드 파일이 1GB를 초과하는 경우 (압축되지 않음) 파일을 여러 파일로 분할합니다.
항목 유형 (예: tvseries.json, tvseasons.json, tvepisodes.json, movies.json 등)별로 파일을 만드는 것이 좋습니다.
이러한 파일 중 하나가 1GB를 초과하면 항목을 여러 파일 (예: tvepisodes_01.json, tvepisodes_02.json 등)로 분할합니다.
파일 크기가 1GB 미만이면 단일 파일에 포함할 수 있는 항목 수에 제한이 없습니다.
JSON 사양에 따라 파일이 BOM 없이 인코딩되었는지 확인합니다. Linux OS를 확인하려면 hexdump file.json | head -n 1가 주소 0x00에서 BBEF로 시작해서는 안 됩니다.
피드의 유형
프로덕션 피드
Google에 출시하려는 전체 카탈로그를 함께 나타내는 JSON 피드 파일 세트를 나타냅니다. 아래 섹션에서 피드를 만드는 방법을 알아보세요.
Google과 처음 통합하는 경우에만 필요한 피드입니다.
이 피드가 Google에 제출되면 최종적으로 처리 및 출시되기 전에 캡처되는 정보의 양과 정확성에 관해 더 높은 품질 기준을 달성하기 위해 광범위하게 분석되고 몇 번 반복됩니다.
스테이징 피드
프로덕션 피드를 확장해야 하는 특정 사용 사례가 있습니다. 이러한 시나리오의 몇 가지 예는 다음과 같습니다.
이전에 출시되지 않은 새로운 항목 유형을 포함하도록 피드를 확장했습니다.
새 언어로 출시할 수많은 새 항목/메타데이터를 포함하도록 피드를 확장했습니다.
피드를 새로운 플랫폼 유형으로 확장합니다. 예를 들어 프로덕션 피드가 Google 검색에서만 출시되었는데 이제 Google TV로 출시를 확대하려는 경우
이 경우 스테이징 피드가 필요합니다. 이 피드는 프로덕션 피드의 사본이지만 새 플랫폼의 딥 링크, 새 언어의 메타데이터 등 추가 메타데이터가 포함되어 있습니다.
프로덕션 피드와 마찬가지로 캡처되는 정보의 양과 정확성에 관해 더 높은 품질 기준을 달성하기 위해 광범위하게 분석되고 여러 번 반복됩니다.
품질 기준을 달성하면 이 피드가 현재 프로덕션 피드를 대체하여 새 프로덕션 피드가 됩니다.
이 피드를 사용하면 프로덕션 피드에 영향을 주지 않고 초기 실행을 추가 실행과 분리하고 필요한 모든 테스트를 실행할 수 있습니다. 이렇게 하면 최종 사용자 환경이 중단되지 않습니다.
[null,null,[],[[["\u003cp\u003eThe Media feed is a JSON object that contains media content, and onboarding begins with developing and hosting these feeds.\u003c/p\u003e\n"],["\u003cp\u003eFeed files must be in \u003ccode\u003e.json\u003c/code\u003e format, UTF-8 encoded without BOM, unencrypted, and potentially split into multiple files if exceeding 1GB.\u003c/p\u003e\n"],["\u003cp\u003eTwo types of feeds exist: Production feed for initial launch of your entire catalog and Staging feed for subsequent expansions or new platform integrations.\u003c/p\u003e\n"],["\u003cp\u003eBefore creating a full production feed, it is recommended to start with a sample feed, validate it using provided tools, and then expand it to include your entire catalog.\u003c/p\u003e\n"]]],["The initial step in onboarding is developing media feeds, which are JSON files representing your catalog's content. Once developed, these files must be hosted for regular Google fetching. Feed files must be in `.json` format, UTF-8 encoded, unencrypted, and under 1GB (uncompressed); splitting larger files is recommended. Two types exist: production (for initial launch) and staging (for expansion), both are validated and iterated. You should start with a small sample feed for validation, then use tools to validate it, and expand to a production feed.\n"],null,["# Create a feed\n\nThe Media feed is a JSON object that contains a collection of entities that represent the\nmedia content in your catalog, such as TV Series, Movies, Songs, Albums, and more. The first step in\nthe onboarding process is to start developing your feeds. Once the files are ready, you need to [host](./host-the-feed)\nthe feed using one of the supported hosting methods for Google to fetch regularly.\n| **Note:** If you haven't gathered all the required information for your content, see the [Collect Information](../collect-information/) section.\n\nFeed file format requirements\n-----------------------------\n\nThe following are the requirements for the feed file(s):\n\n- Feed file must have the filename extension `.json`.\n- Don't encrypt your feed file.\n- Encode your feed file in UTF-8 (check your file editor setting).\n\n- Split the file into multiple files if your feed file is larger than 1 GB (uncompressed).\n\n- We recommend you create a file per entity type (for example, `tvseries.json`, `tvseasons.json`, `tvepisodes.json`, `movies.json`, etc).\n\n - If any of these files exceeds 1GB, split its entities into multiple files (for example, `tvepisodes_01.json`, `tvepisodes_02.json`, etc).\n - As long as the file size is less than 1 GB, there is no limitation on how many entities you can include in a single file.\n- Ensure that the file is encoded **without** BOM, as per [JSON specification](https://tools.ietf.org/html/rfc7159#section-8.1). To check on a linux OS, `hexdump file.json | head -n 1` must not start with `BBEF` at address 0x00.\n\nTypes of feeds\n--------------\n\n### Production feed\n\n- This represents the set of json feed file(s) that together represent your entire catalog you want to launch on Google. You can learn how to create a feed in the section below.\n- This is the only feed you need if you are integrating with Google for the first time.\n- Once this feed is submitted to Google, it will be extensively analyzed and iterated on a few times to achieve a higher quality bar w.r.t the amount of information being captured and its correctness before it is finally ingested and launched.\n\n### Staging feed\n\n- There are certain use cases that require the expansion of the production feed. A few examples of such scenarios are:\n - Expansion of the feed to include new entity types, not previously launched.\n - Expansion of the feed to include a huge number of new entities/metadata to launch in new locales.\n - Expansion of the feed to new platform types. For example, when the production feed is only launched on Google Search and now you want to expand the launch to Google TV.\n- In such cases, a staging feed is required. This feed is a copy of the production feed except that it has additional metadata, for example, deep links for a new platform, metadata for a new locale and so on.\n- Similar to the production feed, this will be extensively analyzed and iterated on a few times to achieve a higher quality bar w.r.t the amount of information being captured and its correctness. Once the quality bar is achieved, this feed replaces the current production feed to become the new production feed.\n- This feed allows us to separate the initial launch from the additional launches, perform all required testing, without affecting the production feed. This ensures no disruptions to the end user experience.\n\nWork with your Google representative to clarify any questions you may have on the above.\n\nCreate a feed file\n------------------\n\nFollow these best practices when creating the feed:\n\n1. [Create a sample feed using a small set of entities](#create_a_sample_feed)\n\n Before building a feed that contains all the content in your catalog, we recommend you create a\n sample feed with only a small set of entities. While working on your feed, you're likely to run into\n issues. By limiting your the size of the set of entities, you will be able to debug these errors and\n warnings more easily.\n2. [Validate the sample feed](#validate_the_sample_feed)\n\n We provide tools that ensure that your feed is compliant with the specifications. We recommend\n you use these tools to resolve all the errors and warnings found in your sample feed.\n3. [Create a production feed](#create_a_production_feed)\n\n After you've verified that you have a good structure for the small set of your entities, develop a feed for your entire catalog.\n\n### Create a sample feed\n\n1. Select one representative entity from your catalog. Choose an entity with a reasonably complex structure, but is still typical for an entity in the catalog.\n 2. Use the [Data Feed Validation tool](https://actions.google.com/tools/feed-validator/u/0/) to check for syntax errors and missing required properties. (See the next section for details.) Example of a feed with a single `Movie` entity \n\n ```carbon\n {\n \"@context\": \"http://schema.org\",\n \"@type\": \"DataFeed\",\n \"dateModified\": \"2018-07-20T00:44:51Z\",\n \"dataFeedElement\": [\n {\n \"@context\": [\"http://schema.org\", {\"@language\": \"en\"}],\n \"@type\": \"Movie\",\n \"@id\": \"http://www.example.com/my_favorite_movie\",\n \"url\": \"http://www.example.com/my_favorite_movie\",\n \"name\": \"My Favorite Movie\",\n \"potentialAction\": {\n \"@type\": \"WatchAction\",\n \"target\": {\n \"@type\": \"EntryPoint\",\n \"urlTemplate\": \"http://www.example.com/my_favorite_movie?autoplay=true\",\n \"inLanguage\": \"en\",\n \"actionPlatform\": [\n \"http://schema.org/DesktopWebPlatform\",\n \"http://schema.org/MobileWebPlatform\",\n \"http://schema.org/AndroidPlatform\",\n \"http://schema.org/AndroidTVPlatform\",\n \"http://schema.org/IOSPlatform\",\n \"http://schema.googleapis.com/GoogleVideoCast\"\n ]\n },\n \"actionAccessibilityRequirement\": {\n \"@type\": \"ActionAccessSpecification\",\n \"category\": \"subscription\",\n \"requiresSubscription\": {\n \"@type\": \"MediaSubscription\",\n \"name\": \"Example Package\",\n \"commonTier\": true,\n \"@id\": \"[partner determined string]\"\n },\n \"availabilityStarts\": \"2018-07-21T10:35:29Z\",\n \"availabilityEnds\": \"2019-10-21T10:35:29Z\",\n \"eligibleRegion\": [\n {\n \"@type\": \"Country\",\n \"name\": \"US\"\n },\n {\n \"@type\": \"Country\",\n \"name\": \"CA\"\n }\n ]\n }\n },\n \"sameAs\": \"https://en.wikipedia.org/wiki/my_favorite_movie\",\n \"releasedEvent\": {\n \"@type\": \"PublicationEvent\",\n \"startDate\": \"2008-01-20\",\n \"location\": {\n \"@type\": \"Country\",\n \"name\": \"US\"\n }\n },\n \"description\": \"This is my favorite movie.\",\n \"actor\": [\n {\n \"@type\": \"Person\",\n \"name\": \"John Doe\",\n \"sameAs\": \"https://en.wikipedia.org/wiki/John_Doe\"\n },\n {\n \"@type\": \"Person\",\n \"name\": \"Jane Doe\",\n \"sameAs\": \"https://en.wikipedia.org/wiki/Jane_Doe\"\n }\n ],\n \"identifier\": [\n {\n \"@type\": \"PropertyValue\",\n \"propertyID\": \"IMDB_ID\",\n \"value\": \"tt0123456\"\n }\n ]\n }\n ]\n }\n ```\n\n### Validate the sample feed\n\nThe following tools are available to help you validate a sample feed with Google's structured data\nspecifications for media feeds.\n\n- **Data Feed Validation tool**\n\n The Data Feed Validation tool can validate a single entity at a time. Use this tool to validate a sample\n entity from your catalog for structural errors and common content errors. You can find more\n details about the tool [here](../tools/troubleshoot-using-the-data-feed-validation-tool).\n- **JSON Schema Validation tool**\n\n The JSON Schema Validation tool can validate all files in a feed. Use this tool during the\n development of the feed to avoid common structural errors. You can find more details about the\n tool [here](../tools/jsonschemas).\n\n### Create a production feed\n\n1. Once all the errors and warnings in the sample feed are resolved, expand the feed to include all the entities in your catalog.\n2. Use the [Data Feed Validation tool](https://actions.google.com/tools/feed-validator/u/0/) frequently to validate a small number of entities in your feed at a time (Pasting a large number of entities on the tool may freeze the web browser). Confirm that your feed includes all the entities in your catalog by comparing the number of entities in your feed with the number of items in your catalog."]]
